F@H - anyone having trouble connecting to the work server?

MichaelD

Lifer
Jan 16, 2001
31,528
3
76
This started at about 6:00PM, CST. I completed a WU and it couldn't connect to report the WU, but yet it could connect to get more work. :confused:

Then about 20 minutes ago, another box completed a WU; same thing. I've got two WUs queued up to turn in, but I can't connect.

Obviously, there's nothing wrong w/my internet connection. Ideas? Info?
 

kb3edk

Senior member
Jul 11, 2004
494
0
0
No problems connecting to the server lately, but today has still been a weird day. Gotta love Mondays :roll: I saw some unusual messages working on p730 and p736 (see log file below)... they quit early but I still got a couple dozen points :) Unlike the new proteins Martin Trevino is having problems with, these ones have been around for a while. My best guess is Stanford is tweaking some old simulations and rolling out a few new ones at the same time.

-Adam in Philly

--------------------------------------------------------------------------------------------------
[19:32:45] Writing local files
[19:32:45] Completed 1000000 out of 10000000 steps (10)
[19:34:32] Writing local files
[19:34:32] Completed 1100000 out of 10000000 steps (11)
[19:36:19] Writing local files
[19:36:19] Completed 1200000 out of 10000000 steps (12)
[19:38:04] Quit 101 - Fatal error:
[19:38:04] Step 1295542, time 1.78259e+006 (ps) LINCS WARNING
[19:38:04] relative constraint deviation after LINCS:
[19:38:04] max 444804.031250 (between atoms 26 and 30) rms 58772.121094
[19:38:04]
[19:38:04] Simulation instability has been encountered. The run has entered a
[19:38:04] state from which no further progress can be made.
[19:38:04] If you often see other project units terminating early like this
[19:38:04] too, you may wish to check the stability of your computer (issues
[19:38:04] such as high temperature, overclocking, etc.).
[19:38:04] Going to send back what have done.
[19:38:04] logfile size: 18210
[19:38:04] - Writing 18905 bytes of core data to disk...
[19:38:04] ... Done.
[19:38:04]
[19:38:04] Folding@home Core Shutdown: EARLY_UNIT_END
 

GLeeM

Elite Member
Apr 2, 2004
7,199
128
106
Sometimes a server gets over-busy. Your GUI client will try again to send later (every 6 hours, I think) and when the next WU is sent also.

The new WU probably came from a different server.

You could try to send now with a special "send all" shortcut. Go to the install dir, right click winFAH.exe and select Create Shortcut. Rename it - send all. Right click your new shortcut and select Properties. In the Target textbox, at the right of whats in there, add a space, a dash and send all, like this:
"C:\Program Files\Folding@Home\winFAH.exe" -send all
You will have to quit the GUI, then double click your send all shortcut, it will try to send WUs and then quit. Restart your GUI, and check the queue.

:)
 

MichaelD

Lifer
Jan 16, 2001
31,528
3
76
Thanks guys. It finally went. Went overnight sometime, all by itself. :)

Currently #144 on TeamAT. :D And climbing. *I think I can, I think I can, I think I can* ;) Have a good day.