Bad WU 1455X

[WhitehawkEQ]

Is anyone else getting bad WU's in the 14550-14555 range?

20:54:47:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:07:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:25:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:41:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:56:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:05:48:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
******************************* Date: 2020-03-18 *******************************
20:54:47:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:07:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:25:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:41:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:56:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:05:48:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
******************************* Date: 2020-03-18 *******************************
20:54:47:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:07:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:25:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:41:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
20:55:56:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:05:48:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:16:05:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)

 

[Holdolin]

Yes, the few wu's i was actually able to get were those and they failed....

 

[WhitehawkEQ]

On a positive note, I got this setup:

 

[Holdolin]

Schweet. I just ploped over to seti@home; just to find out they're shutting down at the end of the month. On an unrelated note, one of the pumps on my boiler failed today. Boy what a day. Cheers

 

[HayesK]

Is anyone else getting bad WU's in the 14550-14555 range?

p14551 is shown on psummary as a gpu project and no thread in the beta forum about being released for BETA testing. Apparently some new projects escaped from the lab before being ready for release. The project owner has been notified. I am not aware of any gpu projects currently available to beta only. Currently best, and safer, to run the client-type=advanced or no flag at all.

What client-type setting caught the p14551-55?

CORE22 p14551, p14553, p14555 - Immediately Erred Out
https://foldingforum.org/viewtopic.php?f=66&t=32825

 

[Automata]

With "client-type=advanced":

21:38:05:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:38:05:WU01:FS01:Sending unit results: id:01 state:SEND error:FAULTY project:14555 run:0 clone:468 gen:0 core:0x22 unit:0x0000000480fccb025e726eb6c45ea73c

21:38:17:WARNING:WU01:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
21:38:17:WU01:FS01:Sending unit results: id:01 state:SEND error:FAULTY project:14553 run:0 clone:524 gen:0 core:0x22 unit:0x0000000080fccb025e725b177ff86d88

There were a lot more failures for the same projects.

 

[HayesK]

With "client-type=advanced":

There were a lot more failures for the same projects.

Thanks. Added info about on being caught with the advanced setting to thread in the beta testing topic at the Folding Forum.
https://foldingforum.org/viewtopic.php?f=66&t=32825&start=15

 

[rustyfender]

is seti closing down permanently?