Search found 10 matches
- Sun Dec 20, 2020 6:28 pm
- Forum: New Donors start here
- Topic: FahCore returned: INTERRUPTED (102 = 0x66)
- Replies: 3
- Views: 1251
Re: FahCore returned: INTERRUPTED (102 = 0x66)
'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...
- Sun Dec 20, 2020 3:11 pm
- Forum: New Donors start here
- Topic: FahCore returned: INTERRUPTED (102 = 0x66)
- Replies: 3
- Views: 1251
FahCore returned: INTERRUPTED (102 = 0x66)
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: FahCore returned: INTERRUPTED (102 = 0x66) I've tried executing: FAHClient --dump 02 But that results in: ... 15:06:52:Trying to access database... 15:06:52:Successful...
- Sat Jul 18, 2020 2:15 pm
- Forum: New Donors start here
- Topic: What does "Average performance' report ?
- Replies: 1
- Views: 943
What does "Average performance' report ?
While reviewing my log file, I see this kind of message:
2:31:03:WU02:FS01:0x22:Average performance: 54.1693 ns/day
What is it telling me?
Is is that my run simulated an average of 54 ns/day of atomic motion in the structure being analysed?
(So a 2hr job simulated about 4.5ns of movement.)
2:31:03:WU02:FS01:0x22:Average performance: 54.1693 ns/day
What is it telling me?
Is is that my run simulated an average of 54 ns/day of atomic motion in the structure being analysed?
(So a 2hr job simulated about 4.5ns of movement.)
- Mon Jun 01, 2020 10:54 pm
- Forum: New Donors start here
- Topic: HOw do I create a team?
- Replies: 1
- Views: 622
- Mon Jun 01, 2020 10:14 pm
- Forum: Discussions of General-FAH topics
- Topic: stats.foldingathome.org stopped updating
- Replies: 57
- Views: 20017
Re: stats.foldingathome.org stopped updating
It looks like they might be updating again.
My stats just changed!
They aren't as up to date as EOC data, but at least it's changing again.
My stats just changed!
They aren't as up to date as EOC data, but at least it's changing again.
- Mon Jun 01, 2020 1:11 pm
- Forum: Discussions of General-FAH topics
- Topic: stats.foldingathome.org stopped updating
- Replies: 57
- Views: 20017
Some stats locations not being updated
I've got machines folding non-stop, but yesterday my stats haven't been updating, at least in some viewers. The web control, browser viewer, hasn't changed its view of my total points in about 12 hours. My https://stats.foldingathome.org/donor/Fulko_Hew page is similarly out of date, as well as my i...
- Tue Apr 21, 2020 5:29 pm
- Forum: New Donors start here
- Topic: FAHClient throws exception (Fedora 26)
- Replies: 4
- Views: 3093
Re: FAHClient throws exception (Fedora 26)
I have opened a bug report on GitHub, on this issue (#1411).
- Tue Apr 21, 2020 3:48 pm
- Forum: New Donors start here
- Topic: FAHClient throws exception (Fedora 26)
- Replies: 4
- Views: 3093
Re: FAHClient throws exception (Fedora 26)
More information: 1/ It turns out that FAHViewer ALSO causes FAHClient to throw the same exception A set of 3 exceptions every 5 seconds. In this case, so as to not confuse symptoms, I started the FAHViewer directly without using FAHControl (Because FAHControl on it own causes Client to throw the ex...
- Sun Apr 19, 2020 3:53 am
- Forum: New Donors start here
- Topic: FAHClient throws exception (Fedora 26)
- Replies: 4
- Views: 3093
Re: FAHClient throws exception (Fedora 26)
There is nothing unusual in the log. It and the client proceeds normally. And as soon as I start FAHControl, and it connects to FAHClient, the client starts spewing the exception every ~2 seconds. Stopping FAHControl stops the exception... restarting FAHControl restarts the exception. Note that havi...
- Sat Apr 18, 2020 5:57 pm
- Forum: New Donors start here
- Topic: FAHClient throws exception (Fedora 26)
- Replies: 4
- Views: 3093
FAHClient throws exception (Fedora 26)
I just upgraded to version 7.6.9 and when the FAHControl is running, the FAHClient emits the following message onto its stdout/stderr every 2-3 seconds: 17:52:10:ERROR:std::exception: std::bad_cast And stopping FAHClient quiets FAHControl. Fortunately, everything else seems to work. (Running on Fedo...