Folding Forum

Thanks for the quick reply, and it seemed like a good idea, but it didn't work. In the course of trying to diagnose this thing, I loaded FahMon on the machine that's reported as "Hung" to see if it would work on its "own" system, so to speak, but it reports as "Hung" there too, also with the progress updating correctly.

ArVee wrote:I apologize if this has already been covered; I did search Help and the forum before posting. FahMon is reporting a Linux SMP unit that is folding under VMWare on a Windows machine as "hung." The unit is not hung, and FahMon even shows the updated percentage progress while showing the ETA as Hung. Any ideas?

I have this issue fairly often. Check Ignore Asynchronous Clocks can help but it seems to have a mind of its own. Sometimes quiting the FahMon and opening it works, and sometimes rebooting the monitoring machine works.

FahSpy seems to handle VM clients better, but doesn't have the nice web output or previous WU data that FahMon has. I run both

Hi again, TheMASS

Clicking the box and quitting and re-starting didn't work, so possibly it's a bug and I assume it's been reported and documented, or if not, UncleFungus will certainly see it here. My chief concern was that the nf setup wasn't working properly, but that's not it, and I can get the output from that machine fine from FahMon, so I'm happy. I just wanted it ALL once I saw the nice interface, lol.

P.S. I like the increased output from nf so much that as other machines finish their current WU's it's going on them too. One's due in an hour and a half. Fold on.

Update: I added a second client to monitor and the clock times it's picking up are just crazy. On a p2653, it's showing frame times of almost 90 minutes when real time is about 23 minutes. This applies to the log as well, it's showing the clock galloping along at 3x reality. ETA and PPD are of course out accordingly. The one spot it appears to be accurate is under Benchmarks - Eff. Time/Frame; Min., Avg., Curr., and R3F all relect the crazy numbers.
Let me know if I can provide further specifics.

Sorry, neglected to mention that it's monitoring notfred under VMWare Player.

ArVee wrote:Sorry, neglected to mention that it's monitoring notfred under VMWare Player.

sorry for being blind if you mentioned it already, but did you check the 'ignore asynchronous clocks' in Settings> Monitoring tab?
this usually helps.


Besides that, I have one tidbit
After PC reboot fahmon forgets the sizes of the columns in main window need to reset them everytime I reboot.
And I had this problem that sometimes when you clock the tray icon it maximizes the window(makes it big, very big and covers all desktop). Deleting config file helps. but the strange thing is, that when I delete config file, most of the settings are still as before. i just need to change some Monitoring settings and that's it. yeah it has the mind of it's own
By the way version is the latest one 2.3.2a I think

The box is ticked off, and I tried it unchecked, too, no change in the clock being on steroids. Thanks for the other tips, I'll know how to fix them if they crop up. I think later on tonight I'll try FahSpy to see if the problem is deeper, perhaps in the Linux-notfred-vmware setup, as it seems a little odd to me that with almost identical boxes, same setup, same protein, one would have the problem and one not have it.

Edit Update: I'm now pretty sure it's not FahMon that's still causing the haywire clock, because when I browse to the instance of folding under a browser, the log file shows the exact same problem.

ArVee wrote:The box is ticked off, and I tried it unchecked, too, no change in the clock being on steroids. Thanks for the other tips, I'll know how to fix them if they crop up. I think later on tonight I'll try FahSpy to see if the problem is deeper, perhaps in the Linux-notfred-vmware setup, as it seems a little odd to me that with almost identical boxes, same setup, same protein, one would have the problem and one not have it.

Edit Update: I'm now pretty sure it's not FahMon that's still causing the haywire clock, because when I browse to the instance of folding under a browser, the log file shows the exact same problem.

so something is loading your cpu and it is not fah

FahMon 2.3.2a is giving me an error message when I select "Download New Projects":
"The line 166 is not correctly formatted!" and some html tags.
Is anyone else seeing this same?

kjk wrote:FahMon 2.3.2a is giving me an error message when I select "Download New Projects":
"The line 166 is not correctly formatted!" and some html tags.
Is anyone else seeing this same?

Yes I have the same message.

Line 169 for me.

Got p2619 for the first time and tried to download new projects. Got this message:



But it seemed to get the projects anyway, so at least it's working. Tried to google the error and search the forum for it, but didn't find anything. What is it?

The number of frames are missing for a few projects in the 2790 range as well as the points. See project summary at top of this forum.

Ignore the warning, it's just telling you that some lines on psummary aren't formatted in the way FahMon expects. The reason is that a number of GPU WUs have appeared on psummary without a frame count (and with an incorrect core), but to my knowledge these are test WUs that will not be assigned anyway (atm at least).

Whow, this was fast! Thanks uncle_fungus and others. I thought that it's not too serious issue but wanted to see if others are seeing this.