• 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.

Weird Issue With Folding@Home Client

A

AMD_RULES

2[H]4U
Joined
Mar 26, 2007
Messages
3,010
On one of my folding rig, once a work unit is complete, the client shuts itself down.
What is causing this? The computer is running Server 03 and has been on for over a week.
Should I reboot?

Any ideas?

Thanks!! :)
 
Is this the standard 504 console client? I've got a couple old stock P4 1.8's that do that about once / twice a month. The machines never reboot, but for some reason the client windows closes and everything. I restart the client, and it picks right back up where it left off with no issue.

I've never figured out why, and wondered if it wasn't faulty hardware, but like I mentioned above, they run stock.

 
It's possible that when you did -config you told the client to do that. If you are running as a service it's possible that is not configured properly.

I'm assuming by shutting down you mean complete shutdown like you turned it off. If the window stays open but everything just stops double check network connections.

In any event a good reboot never hurts a thing, clears the ram and all that good stuff;)

 
Code: 
[10:51:18] + Attempting to send results
[10:51:49] + Results successfully sent
[10:51:49] Thank you for your contribution to Folding@Home.
[10:51:49] + Number of Units Completed: 5

[10:53:53] - Preparing to get new work unit...
[10:53:53] + Attempting to get work packet
[10:53:53] - Connecting to assignment server
[10:53:54] - Successful: assigned to (0.0.0.0).
[10:53:54] + News From Folding@Home: Welcome to Folding@Home
[10:53:54] Work Unit has an invalid address.
[10:53:54] - Error: Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[10:54:13] + Attempting to get work packet
[10:54:13] - Connecting to assignment server
[10:54:14] - Successful: assigned to (0.0.0.0).
[10:54:14] + News From Folding@Home: Welcome to Folding@Home
[10:54:14] Work Unit has an invalid address.
[10:54:14] - Error: Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[10:54:36] + Attempting to get work packet
[10:54:36] - Connecting to assignment server
[10:54:37] - Successful: assigned to (0.0.0.0).
[10:54:37] + News From Folding@Home: Welcome to Folding@Home
[10:54:37] Work Unit has an invalid address.
[10:54:37] - Error: Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[10:55:00] + Attempting to get work packet
[10:55:00] - Connecting to assignment server
[10:55:00] - Successful: assigned to (0.0.0.0).
[10:55:00] + News From Folding@Home: Welcome to Folding@Home
[10:55:00] Work Unit has an invalid address.
[10:55:00] - Error: Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[10:55:48] + Attempting to get work packet
[10:55:48] - Connecting to assignment server
[10:55:48] - Successful: assigned to (0.0.0.0).
[10:55:48] + News From Folding@Home: Welcome to Folding@Home
[10:55:48] Work Unit has an invalid address.
[10:55:48] - Error: Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.
[10:57:20] + Attempting to get work packet
[10:57:20] - Connecting to assignment server
[10:57:20] - Successful: assigned to (0.0.0.0).
[10:57:20] + News From Folding@Home: Welcome to Folding@Home
[10:57:20] Work Unit has an invalid address.
[10:57:20] - Error: Attempt #6  to get work failed, and no other work to do.
             Waiting before retry.
[11:00:02] + Attempting to get work packet
[11:00:02] - Connecting to assignment server
[11:00:03] - Successful: assigned to (0.0.0.0).
[11:00:03] + News From Folding@Home: Welcome to Folding@Home
[11:00:03] Work Unit has an invalid address.
[11:00:03] - Error: Attempt #7  to get work failed, and no other work to do.
             Waiting before retry.
[11:05:32] + Attempting to get work packet
[11:05:32] - Connecting to assignment server
[11:05:33] - Successful: assigned to (171.64.65.63).
[11:05:33] + News From Folding@Home: Welcome to Folding@Home
[11:05:33] Loaded queue successfully.
[11:05:35] + Closed connections
[11:05:35] 
[11:05:35] + Processing work unit
[11:05:35] Core required: FahCore_a1.exe
[11:05:35] Core found.
[11:05:35] Working on Unit 06 [April 20 11:05:35]
[11:05:35] + Working ...
[11:05:35] 
[11:05:35] *------------------------------*
[11:05:35] Folding@Home Gromacs SMP Core
[11:05:35] Version 1.74 (March 10, 2007)
[11:05:35] 
[11:05:35] Preparing to commence simulation
[11:05:35] - Looking at optimizations...
[11:05:35] - Created dyn
[11:05:35] - Files status OK
[11:05:36] - Expanded 608260 -> 3255645 (decompressed 535.2 percent)
[11:05:36] - Starting from initial work packet
[11:05:36] 
[11:05:36] Project: 3062 (Run 4, Clone 87, Gen 16)
[11:05:36] 
[11:05:36] Assembly optimizations on if available.
[11:05:36] Entering M.D.
[11:05:53] 2 percent)
[11:05:53] - Starting from initial work packet
[11:05:53] 
[11:05:53] Project: 3062 (Run 4, Clone 87, Gen 16)

Every box is doing this. so don't fret they eventually do get a new WU just may take a bit... Wasting 15-30 FTL!

 
Axdrenalin said:
Is this the standard 504 console client? I've got a couple old stock P4 1.8's that do that about once / twice a month. The machines never reboot, but for some reason the client windows closes and everything. I restart the client, and it picks right back up where it left off with no issue.

I've never figured out why, and wondered if it wasn't faulty hardware, but like I mentioned above, they run stock.

Click to expand...
Yes it is...
BillR said:
It's possible that when you did -config you told the client to do that. If you are running as a service it's possible that is not configured properly.

I'm assuming by shutting down you mean complete shutdown like you turned it off. If the window stays open but everything just stops double check network connections.

In any event a good reboot never hurts a thing, clears the ram and all that good stuff;)

Click to expand...

When I say "shutdown," the whole window closes and the tray icon disappears.
For the network, it is currently getting a DHCP address. Should I set a static one?
 
AMD_RULES said:
Yes it is...


When I say "shutdown," the whole window closes and the tray icon disappears.
For the network, it is currently getting a DHCP address. Should I set a static one?
Click to expand...

If you are rebooting machines from time to time yes, I did that with my little farm and it helped a lot. I even went so far as to disable DHCP on my router, not so much for Folding but as just one more security measure.

When ever you see trying to connect to 0.0.0.0 that is a problem on Stanford’s end not your end.

As for the whole client shutting down the only thing that crosses my mind at the moment is delete the old client after it finishes its next WU and do a reinstall.

I do know several members have had issues with stopping the client and experiencing a total loss of all work done, a reinstall usually fixes this.

For lack of a better answer look here:

http://www.google.com/search?source...+smp+folding+client+shuts+down+after+one+unit

Luck man, sorry I couldn’t be of more help


 
BillR said:
If you are rebooting machines from time to time yes, I did that with my little farm and it helped a lot. I even went so far as to disable DHCP on my router, not so much for Folding but as just one more security measure.

When ever you see trying to connect to 0.0.0.0 that is a problem on Stanford’s end not your end.

As for the whole client shutting down the only thing that crosses my mind at the moment is delete the old client after it finishes its next WU and do a reinstall.

I do know several members have had issues with stopping the client and experiencing a total loss of all work done, a reinstall usually fixes this.

For lack of a better answer look here:

http://www.google.com/search?source...+smp+folding+client+shuts+down+after+one+unit

Luck man, sorry I couldn’t be of more help


Click to expand...
Thanks for your input man. I appreciated it!
I'll reinstall the client once the WU is complete... :)
 
AMD_RULES said:
Thanks for your input man. I appreciated it!
I'll reinstall the client once the WU is complete... :)
Click to expand...

And speaking of the 0.0.0.0 error, Stanford is out of work on a few servers. I have three clients displaying that error.;)
 
I hit the "No work to do" error message earlier today. Got a couple of rounds of CoD4 in while waiting.

Actually, it still hasn't cleared up either... annoying.
 
Yeah I had one computer with out work for 4 hrs... what a waste!!! Grrr

 
On my main rig, I have two VM instances of Linux SMP. One of them had that message for nearly 4 hours. I learned a few days ago, I wasn't using 100% with the two VMs. So I added one F@H client. Still not at 100%, so I went ahead and added 3 more. All on idle CPU cycles and now I have 2 Linux SMP clients and 4 F@H clients and they are all playing nice (truly amazing actually). I'm finally at 100% utilization.

When one of the SMP clients picked up the No Work to do, the F@H clients associated with that VM went into over drive so at least those cores were being utilized and doing something. The F@H console deadlines are way longer so even with the spare cycles from the VMs, I'm still meeting preferred deadlines.

 
probably just a quirk of windows. my internet windows will occasionaly vanish. seti still runs though ;)
 
You must log in or register to reply here.
Back
Top