Died with the warning.
[17:29:17] Warning: long 1-4 interactions
[17:29:21] CoreStatus = 1 (1)
[17:29:21] Client-core communications error: ERROR 0x1
[17:29:21] Deleting current work unit & continuing...
[17:33:42] - Warning: Could not delete all work unit files (1): Core returned invalid code
Then it hung for a day.
Queue and work dir removed, client restarted, all is well so far.
Project: 3064 (Run 4, Clone 45, Gen 63)
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 390
- Joined: Sun Dec 02, 2007 4:53 am
- Hardware configuration: FX8320e (6 cores enabled) @ stock,
- 16GB DDR3,
- Zotac GTX 1050Ti @ Stock.
- Gigabyte GTX 970 @ Stock
Debian 9.
Running GPU since it came out, CPU since client version 3.
Folding since Folding began (~2000) and ran Genome@Home for a while too.
Ran Seti@Home prior to that. - Location: UK
- Contact:
-
- Posts: 390
- Joined: Sun Dec 02, 2007 4:53 am
- Hardware configuration: FX8320e (6 cores enabled) @ stock,
- 16GB DDR3,
- Zotac GTX 1050Ti @ Stock.
- Gigabyte GTX 970 @ Stock
Debian 9.
Running GPU since it came out, CPU since client version 3.
Folding since Folding began (~2000) and ran Genome@Home for a while too.
Ran Seti@Home prior to that. - Location: UK
- Contact:
Re: Project: 3064 (Run 4, Clone 45, Gen 63)
Somehow i managed to get the same workunit again. It died at 9% some time yesterday. Same error as above.
Same action taken.
Same action taken.
Re: Project: 3064 (Run 4, Clone 45, Gen 63)
Hi there,
Thanks for the report. Will keep track of this.
Paula
Thanks for the report. Will keep track of this.
Paula
-
- Site Moderator
- Posts: 6395
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: Project: 3064 (Run 4, Clone 45, Gen 63)
No one has returned this WU yet ... it might be a bad one