Page 1 of 1

FahCore returned: INTERRUPTED (102 = 0x66)

Posted: Sun Dec 20, 2020 3:11 pm
by fhew
I've just noticed that the WU running on my CPU slot has been restarting every minute
for the past few days, with the error message:

Code: Select all

FahCore returned: INTERRUPTED (102 = 0x66)
I've tried executing:

Code: Select all

FAHClient --dump 02
But that results in:

Code: Select all

...
15:06:52:Trying to access database...
15:06:52:Successfully acquired database lock
15:06:52:Enabled folding slot 00: PAUSED cpu:4 (by user)
15:06:52:ERROR:Exception: Could not bind socket to 0.0.0.0:7396: Address already in use
15:06:52:ERROR:Exception: Could not bind socket to 0.0.0.0:36330: Address already in use
15:06:52:Unit processing completed
15:06:52:Clean exit
But it doesn't change anything, It's still in the loop.
I see that the WU is scheduled to expire at 2020-12-21T13:12:00Z
I suppose I could wait and see what happens, but it is pointless to
continue the way it (isn't) running right now.

Code: Select all

Project: 16926 (Run 77, Clone 516, Gen 8)
Suggestions welcome.

Re: FahCore returned: INTERRUPTED (102 = 0x66)

Posted: Sun Dec 20, 2020 4:22 pm
by Joe_H
The dump command in that format works only if the background FAHClient process has been exited and the correct paths have been set with the other command options or by executing the command from the right directory. With the background FAHClient running you would need to use "FAHClient --send ..." to pass a command to that background process. I have not used that method in a while, so don't recall the rest of the details.

For this specific project, no need to wait on dropping the WU. There is a known problem with that project.

Re: FahCore returned: INTERRUPTED (102 = 0x66)

Posted: Sun Dec 20, 2020 4:36 pm
by bruce
What version of FAHClient are you running?

I'd probably reinstall the client, if only to clean out the looping code.

Re: FahCore returned: INTERRUPTED (102 = 0x66)

Posted: Sun Dec 20, 2020 6:28 pm
by fhew
'bruce'... restarting the client (version 7.6.9) didn't change anything.

Thanks Joe_H for the suggestion.
I thought --dump was a command sent to the running client. No wonder it didn't work.
(I never tried it when it wasn't running already.)
I ended up deleting the directory for that work queue, and restarted the client.
That cleared the problem.