• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Folding@home Core Shutdown: INTERRUPTED

O

owkia

Supreme [H]ardness
2FA
Joined
May 27, 2007
Messages
5,414
I've received this error at least 3 or 4 times now on my Suse client running in VMware, but have never had this problem in all the time that I've been running the windows client. I just got it twice on the same work unit; once just after 60% and then again right after it reached 100%, but before it actually sent the completed work back.

It doesn't delete the WU so restarting the client gets it running again without any problems. It's good that I'm not losing any work, but it's quite annoying waking up in the morning to find that it only made an extra 5% progress before shutting down in the middle of the night for no reason.

It's also not giving me any sort of Core Status error along with that error. A quick Google seems to show a lot of people getting a Core Status: 66 error at the same time, but I'm not getting that. I'm only getting the INTERRUPTED error and it leaves my WU untouched.

Does anyone have any idea on what might be constantly causing this on my Linux client, but not on Windows?


 
owkia said:
Does anyone have any idea on what might be constantly causing this on my Linux client, but not on Windows?
Click to expand...

I get something like that on the very odd occasion.
I clients tend to stop like that if the auto-send happens at the same time as a frame save.
So it could be a bug in the program but you need to be very unlucky to hit it often.

Are you running "-verbosity 9" so you log file shows the auto-send ?

Luck .............. :D
 
Looking at the log, it seems as if the autosend happened at around 4 minutes 15 seconds after the Interrupted error both times on this one WU. The autosend doesn't seem to be happening at the same time as a frame save though from what I'm seeing.
 
I've gotten the Core Status 66 error a couple times now. According to the FaHWiki, there's a possibility it is caused by some hibernation/screen-lock or logout procedures. This seems to apply more to the GPU client from what I can tell, but Suse does log me out automatically so it can't hurt to try disabling it. The question is, how do I go about disabling the auto-logout feature? I assume it's possible, but I can't figure out where it is. Like many others here, Linux isn't really my thing. I've looked through the YaST Admin Settings multiple times and can't find anything that appears to have control over this. Regardless of if it fixes the problem, auto-logout annoys me anyway.


 
You must log in or register to reply here.
Back
Top