A strange work unit that crashed as soon as it ran.

Moderators: Site Moderators, FAHC Science Team

Post Reply
whocrazy
Posts: 79
Joined: Thu Mar 27, 2008 9:09 pm

A strange work unit that crashed as soon as it ran.

Post by whocrazy »

21:28:02:WU00:FS00:0xa8:Project: 18491 (Run 25, Clone 49, Gen 35)
21:28:02:WU00:FS00:0xa8:Unit: 0x00000000000000000000000000000000
21:28:02:WU00:FS00:0xa8:Digital signatures verified
21:28:02:WU00:FS00:0xa8:Calling: mdrun -c frame35.gro -s frame35.tpr -x frame35.xtc -cpt 3 -nt 16 -ntmpi 1
21:28:02:WU00:FS00:0xa8:Steps: first=170000000 total=175000000
21:28:02:WU00:FS00:0xa8:Completed 1 out of 5000000 steps (0%)
21:28:03:WARNING:WU00:FS00:FahCore returned an unknown error code which probably indicates that it crashed
21:28:03:WARNING:WU00:FS00:FahCore returned: UNKNOWN_ENUM (-1073741819 = 0xc0000005)
Can anyone tell me what might be going on here?
After I pressed CTRL c and reran the program again, a new work unit was downloaded (Project: 18492 (Run 7, Clone 55, Gen 51) and is now running as normal, but I would like to know why the other WU wouldn't run?
Thanks.
bikeaddict
Posts: 144
Joined: Sun May 03, 2020 1:20 am

Re: A strange work unit that crashed as soon as it ran.

Post by bikeaddict »

This WU failed for everyone who tried to run it. It may be a bad task or it might have been expected to fail by design.

https://apps.foldingathome.org/wu#proje ... =49&gen=35
whocrazy
Posts: 79
Joined: Thu Mar 27, 2008 9:09 pm

Re: A strange work unit that crashed as soon as it ran.

Post by whocrazy »

but why would they want to do that? make a work unit fail by design as soon as it ran?
that would be crazy making.
Joe_H
Site Admin
Posts: 7793
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: A strange work unit that crashed as soon as it ran.

Post by Joe_H »

Not by design necessarily, but a trajectory may reach an end point or blow up after several Gens. Failed WUs are retried a number of times in case it is from hardware or software issues, then the server is supposed to stop assigning it. I only see 5 assignments and failures, that is a normal stopping point.

In this case the trajectory reached 35 successful iterations, 0 through 34. Other trajectories for this project with different starting conditions may have gone farther, I haven't checked.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Post Reply