Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

171.64.65.102 Reject

https://foldingforum.org/viewtopic.php?t=16492

Page 2 of 3

Re: 171.64.65.102 Reject

Posted: Tue Jan 25, 2011 4:27 pm
by gwildperson
It's working now.

It probably had a late night and needed a cup of coffee. :)

Re: 171.64.65.102 Reject

Posted: Tue Jan 25, 2011 4:34 pm
by Bobcat
I think this server goes out drinking a lot.

It happens enough that I made a DOS batch file to do a send all:

Code: Select all

cd \Users\Bob\AppData\Roaming\Folding@home-gpu
"\Program Files (x86)\Folding@home\Folding@home-gpu\Folding@home.exe" -send all
Yeah, I could have simply made a shortcut, but for some reason I felt like doing this as a batch file.

Re: 171.64.65.102 Reject

Posted: Tue Jan 25, 2011 4:35 pm
by gwildperson
So after the server has been down for a while and it's overloaded trying to catch up you can contribute to the overload....???

Re: 171.64.65.102 Reject

Posted: Tue Jan 25, 2011 4:41 pm
by 7im
The client does a send all when starting. It's hard coded. So unless you really want the client to not run after that batch file, there really is no need for it. ;)

Re: 171.64.65.102 Reject

Posted: Tue Jan 25, 2011 5:25 pm
by Bobcat
7im wrote:The client does a send all when starting. It's hard coded. So unless you really want the client to not run after that batch file, there really is no need for it. ;)
I really do NOT want the client to start a new WU. Because of the prohibition on switching users when running the GPU client, I need to run it only when no one else is around. Since it takes me 8 hours to complete a WU, I need to carefully plan when I start a WU.

The server being down throws an additional complication into my planning. Since it may be days until I can run the GPU client again, waiting until then would cause me to miss the deadline. Hence the need to upload the completed WU without starting a new WU.

If the server was actually reliable (*cough* *cough*), all this trouble could be avoided.

Re: 171.64.65.102 Reject

Posted: Sat Jan 29, 2011 3:37 pm
by drougnor
I hate to say that this server is once again in reject mode as of 2:50:10 PST, per the server stats page.

Re: 171.64.65.102 Reject

Posted: Sat Jan 29, 2011 4:12 pm
by bruce
This looks like the sort of problem that's going to take longer to fix... :(

(But I hope I'm wrong.)

Re: 171.64.65.102 Reject

Posted: Sat Jan 29, 2011 5:01 pm
by drougnor
Thanks for the fast update.

Re: 171.64.65.102 Reject

Posted: Sat Jan 29, 2011 5:04 pm
by VijayPande
Thanks. We're on it. Dr. Lin has fixed this I think.

Re: 171.64.65.102 Reject

Posted: Sat Jan 29, 2011 5:22 pm
by drougnor
I just restarted the client, and work is coming back in. Thanks again!

Re: 171.64.65.102 Reject

Posted: Sat Feb 12, 2011 9:00 am
by GreyWhiskers
Down again. Server stats shows reject - detail stats show reject since 00:05 PST 12 Feb 2011. No work for my ATI GPU.

My client is on long-term hold after 9 consecutive tries to get new work.

Folding@home server status
Report initiated on Sat Feb 12 00:25:10 PST 2011.
Report initiated on Sat Feb 12 00:45:10 PST 2011
171.64.65.102 GPU vspg2v2 vvoelz full Reject

Re: 171.64.65.102 Reject

Posted: Sat Feb 12, 2011 4:37 pm
by GreyWhiskers
Server stats reported the server back up at 0130 12 Feb. My client didn't get a new WU until 2:20 (I had gone to bed and just let it work on auto).

Re: 171.64.65.102 Reject

Posted: Fri Mar 25, 2011 4:37 pm
by GreyWhiskers
Well, it's down again. When I checked my systems this morning, the ATI GPU client had been sitting there from 1356 GMT to 1610 GMT (the latest entry in the HFM report) trying to upload its last completed WU and looking for a new WU. This GPU is on my old HP Costco special AGP bus Pent IV HT uniprocessor that has been prime until I turned on my new Digital Storm beast earlier this week.

I looked at the Stanford server stats, and brought out the snippet below.It looks like the server came up for one of the three-times-an-hour checkpoints in the Stanford server stat history, but the GPU client missed it. After getting so many rejects in a row, the client goes into an every 45 minutes or so polling cycle.

As others have observed, the Stanford server stats don't reflect Daylight savings time - so are showing an hour earlier than our Silicon Valley wall clocks.

Code: Select all

Fri Mar 25 05:35:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Accepting
Fri Mar 25 05:55:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 06:15:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 06:35:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 06:55:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 07:15:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 07:35:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Accepting
Fri Mar 25 07:55:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject

Re: 171.64.65.102 Reject

Posted: Fri Mar 25, 2011 5:51 pm
by GreyWhiskers
Finally came up - Client was able to get a new WU and upload the previously finished WU.

Code: Select all

[16:58:58] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[17:47:06] + Attempting to get work packet
[17:47:06] Passkey found
[17:47:06] - Will indicate memory of 2047 MB
[17:47:06] Gpu type=1 species=3.
[17:47:06] - Connecting to assignment server
[17:47:06] Connecting to http://assign-GPU.stanford.edu:8080/
[17:47:07] Posted data.
[17:47:07] Initial: 40AB; - Successful: assigned to (171.64.65.102).
[17:47:07] + News From Folding@Home: Welcome to Folding@Home
[17:47:07] Loaded queue successfully.
[17:47:07] Gpu type=1 species=3.
[17:47:07] Sent data
[17:47:07] Connecting to http://171.64.65.102:8080/
[17:47:07] Posted data.
[17:47:07] Initial: 0000; - Receiving payload (expected size: 99236)
[17:47:07] Conversation time very short, giving reduced weight in bandwidth avg
[17:47:07] - Downloaded at ~193 kB/s
[17:47:07] - Averaged speed for that direction ~162 kB/s
[17:47:07] + Received work.
[17:47:07] Trying to send all finished work units
[17:47:07] Project: 5734 (Run 3, Clone 579, Gen 258)
[17:47:07] - Read packet limit of 540015616... Set to 524286976.


[17:47:07] + Attempting to send results [March 25 17:47:07 UTC]
[17:47:07] - Reading file work/wuresults_02.dat from core
[17:47:07]   (Read 263805 bytes from disk)
[17:47:07] Gpu type=1 species=3.
[17:47:07] Connecting to http://171.64.65.102:8080/
[17:47:08] Posted data.
[17:47:08] Initial: 0000; - Uploaded at ~258 kB/s
[17:47:08] - Averaged speed for that direction ~256 kB/s
[17:47:08] + Results successfully sent
[17:47:08] Thank you for your contribution to Folding@Home.
[17:47:08] + Number of Units Completed: 252

[17:47:08] + Sent 1 of 1 completed units to the server
[17:47:08] + Closed connections

Re: 171.64.65.102 Reject

Posted: Sat Mar 26, 2011 4:10 am
by GreyWhiskers
Well, down again - second time for today. Hopefully, won't last too long.

Code: Select all

Fri Mar 25 19:15:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Accepting
Fri Mar 25 19:35:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 19:55:11 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject
Fri Mar 25 20:15:10 PST 2011	171.64.65.102	GPU	vspg2v2	vvoelz	full	Reject

Code: Select all

[03:49:44] + Attempting to get work packet
[03:49:44] Passkey found
[03:49:44] - Will indicate memory of 2047 MB
[03:49:44] Gpu type=1 species=3.
[03:49:44] - Connecting to assignment server
[03:49:44] Connecting to http://assign-GPU.stanford.edu:8080/
[03:49:44] Posted data.
[03:49:44] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[03:49:44] + Couldn't get work instructions.
[03:49:44] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
All times are UTC
Page 2 of 3

Powered by phpBB® Forum Software © phpBB Limited