Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 04, 2009 9:16 pm
by Olorin
You were (of course) right kasson. Thank you.
Re: 171.64.65.56 is in Reject status
Posted: Wed Oct 07, 2009 12:49 pm
by MaxFan
Code: Select all
[08:00:44] + Attempting to send results
[08:01:40] Completed 62500 out of 250000 steps (25%)
[08:17:11] Completed 65000 out of 250000 steps (26%)
[08:17:24] - Couldn't send HTTP request to server
[08:17:24] + Could not connect to Work Server (results)
[08:17:24] (171.64.65.56:8080)
[08:17:24] - Error: Could not transmit unit 01 (completed October 7) to work server.
Server seems to be in reject status again I have 5+ smp core a2's in queue that cannot be delivered.
Re: 171.64.65.56 is in Reject status
Posted: Wed Oct 07, 2009 1:16 pm
by kasson
It's accepting and assigning right now, so I would suspect something along the connection between you and the server, unless it's a load problem.
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 11, 2009 8:41 pm
by 314159
This server is down as of 1:38 PDT.
Please help!
Thank you, as always,
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 11, 2009 9:47 pm
by kasson
Restarting now--thanks for the heads up.
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 11, 2009 10:43 pm
by 314159
Looks fine from here.
(quickly removing -oneunit from a few C2D's)
Your
Volunteers, including me,
sincerely appreciate your quick response
Enjoy the balance of your weekend my friend.......
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 17, 2009 3:11 am
by ikerekes
Code: Select all
[02:01:36] DynamicWrapper: Finished Work Unit: sleep=10000
[02:01:46]
[02:01:46] Finished Work Unit:
[02:01:46] - Reading up to 21178224 from "work/wudata_04.trr": Read 21178224
[02:01:46] trr file hash check passed.
[02:01:46] - Reading up to 27678432 from "work/wudata_04.xtc": Read 27678432
[02:01:46] xtc file hash check passed.
[02:01:46] edr file hash check passed.
[02:01:46] logfile size: 187676
[02:01:46] Leaving Run
[02:01:48] - Writing 49194116 bytes of core data to disk...
[02:01:49] ... Done.
[02:01:54] - Shutting down core
[02:01:54]
[02:01:54] Folding@home Core Shutdown: FINISHED_UNIT
[02:05:10] CoreStatus = 64 (100)
[02:05:10] Unit 4 finished with 74 percent of time to deadline remaining.
[02:05:10] Updated performance fraction: 0.741763
[02:05:10] Sending work to server
[02:05:10] Project: 2677 (Run 28, Clone 94, Gen 52)
[02:05:10] + Attempting to send results [October 17 02:05:10 UTC]
[02:05:10] - Reading file work/wuresults_04.dat from core
[02:05:10] (Read 49194116 bytes from disk)
[02:05:10] Connecting to http://171.64.65.56:8080/
[02:05:10] - Couldn't send HTTP request to server
[02:05:10] + Could not connect to Work Server (results)
[02:05:10] (171.64.65.56:8080)
[02:05:10] + Retrying using alternative port
[02:05:10] Connecting to http://171.64.65.56:80/
[02:05:10] - Couldn't send HTTP request to server
[02:05:10] + Could not connect to Work Server (results)
[02:05:10] (171.64.65.56:80)
[02:05:10] - Error: Could not transmit unit 04 (completed October 17) to work server.
[02:05:10] - 1 failed uploads of this unit.
[02:05:10] Keeping unit 04 in queue.
[02:05:10] Trying to send all finished work units
[02:05:10] Project: 2677 (Run 28, Clone 94, Gen 52)
[02:05:10] + Attempting to send results [October 17 02:05:10 UTC]
[02:05:10] - Reading file work/wuresults_04.dat from core
[02:05:10] (Read 49194116 bytes from disk)
[02:05:10] Connecting to http://171.64.65.56:8080/
[02:05:10] - Couldn't send HTTP request to server
[02:05:10] + Could not connect to Work Server (results)
[02:05:10] (171.64.65.56:8080)
[02:05:10] + Retrying using alternative port
[02:05:10] Connecting to http://171.64.65.56:80/
[02:05:10] - Couldn't send HTTP request to server
[02:05:10] + Could not connect to Work Server (results)
[02:05:10] (171.64.65.56:80)
[02:05:10] - Error: Could not transmit unit 04 (completed October 17) to work server.
[02:05:10] - 2 failed uploads of this unit.
Of course the weekend starts.....
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 17, 2009 2:56 pm
by johnph77
Code: Select all
[12:40:23] + Attempting to send results [October 17 12:40:23 UTC]
[12:40:24] - Couldn't send HTTP request to server
[12:40:24] + Could not connect to Work Server (results)
[12:40:24] (171.64.65.111:8080)
[12:40:24] + Retrying using alternative port
[12:40:25] - Couldn't send HTTP request to server
[12:40:25] + Could not connect to Work Server (results)
[12:40:25] (171.64.65.111:80)
[12:40:25] - Error: Could not transmit unit 06 (completed October 16) to work server.
[12:40:25] - Read packet limit of 540015616... Set to 524286976.
[12:40:25] + Attempting to send results [October 17 12:40:25 UTC]
[12:40:25] - Couldn't send HTTP request to server
[12:40:25] (Got status 503)
[12:40:25] + Could not connect to Work Server (results)
[12:40:25] (171.67.108.17:8080)
[12:40:25] + Retrying using alternative port
[12:40:25] - Couldn't send HTTP request to server
[12:40:25] (Got status 503)
[12:40:25] + Could not connect to Work Server (results)
[12:40:25] (171.67.108.17:80)
[12:40:25] Could not transmit unit 06 to Collection server; keeping in queue.
[12:40:27] + Attempting to send results [October 17 12:40:27 UTC]
[12:40:28] - Couldn't send HTTP request to server
[12:40:28] + Could not connect to Work Server (results)
[12:40:28] (171.64.65.111:8080)
[12:40:28] + Retrying using alternative port
[12:40:29] - Couldn't send HTTP request to server
[12:40:29] + Could not connect to Work Server (results)
[12:40:29] (171.64.65.111:80)
[12:40:29] - Error: Could not transmit unit 06 (completed October 16) to work server.
[12:40:29] - Read packet limit of 540015616... Set to 524286976.
[12:40:29] + Attempting to send results [October 17 12:40:29 UTC]
[12:40:29] - Couldn't send HTTP request to server
[12:40:29] (Got status 503)
[12:40:29] + Could not connect to Work Server (results)
[12:40:29] (171.67.108.17:8080)
[12:40:29] + Retrying using alternative port
[12:40:30] - Couldn't send HTTP request to server
[12:40:30] (Got status 503)
[12:40:30] + Could not connect to Work Server (results)
[12:40:30] (171.67.108.17:80)
[12:40:30] Could not transmit unit 06 to Collection server; keeping in queue.
[12:40:30] + Closed connections
And the beat goes on.....
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 17, 2009 7:30 pm
by Ravage7779
Well either you have a network issue between yourself and the server, or the server rebooted itself. I got an a2 about an hour after you posted that.
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 17, 2009 9:01 pm
by johnph77
Ravage7779 wrote:Well either you have a network issue between yourself and the server, or the server rebooted itself. I got an a2 about an hour after you posted that.
Wasn't a network issue here - work units on other servers were being returned normally. I prefer to think someone read our pleas/requests for human intervention and did what was necessary to restore the server to service.
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 17, 2009 9:16 pm
by kasson
The server does have some code to auto-detect this; that was triggered at 20:59 PDT on Friday. Everything looks to be working right now.
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 17, 2009 9:18 pm
by 314159
johnph77 wrote: I prefer to think someone read our pleas/requests for human intervention and did what was necessary to restore the server to service.
My experience is that the "owner" of this server is
extremely conscientious.
I know/suspect that he subscribes to this particular thread and have seen situations such as this corrected promptly over a period of many months.
This includes outages on weekends, holidays, and sometimes even at "weird" hours of the morning (his time).
Read back through this thread and you will see that he appears to be one of the most "Volunteer friendly" folks in the project.
My hat goes off to him!
Edit: 2 seconds later - (note time stamps on the last two posts)
My opinion remains the same.....
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 18, 2009 5:09 am
by johnph77
kasson -
[15:05:42] Project: 6302 (Run 240, Clone 6, Gen 13)
[15:05:42] - Read packet limit of 540015616... Set to 524286976.
[15:05:42] + Attempting to send results [October 17 15:05:42 UTC]
[15:06:36] + Results successfully sent
[15:06:36] Thank you for your contribution to Folding@Home.
[15:06:36] + Number of Units Completed: 305
All is well. Tell Grant I said, "Hello!"
314159 -
Thanks!
Re: 171.64.65.56 is in Reject status
Posted: Tue Oct 20, 2009 2:26 pm
by ikerekes
Tue Oct 20 05:15:10 PDT 2009 171.64.65.56 SMP vspg4 kasson full Reject 0.80 48 0 4 17883 684 0 8.73 2910 2910 7679 5 - - - 88 0 2 2 1 171.64.122.86
171.67.108.25
171.67.108.25 0 0 LX; LX; LX; X; X; X; ; X; LX; LX; LX; XL; LX; LX; LX; L; 1000, 1000, 100000, 1000000, 1000000, 100000; , 1000000, 10000, 10000, 10000, 1000000, 50000, 50000, 50000, 10000 5, 5, 5, 5, 5, 5; , 5, 5, 5, 5, 5, 5, 5, 5, 5 5, 5, 5, 5, 5, 5; , 5, 5, 5, 5, 5, 5 10000, 10000, 10000, 10000, 10000, 10000; , 10000, 10000, 10000, 49, 10000, 10000, 10000, 10000, 10000 200, 200, 64, 200, 200, 200; , 64, 64, 64, 64, 64, 64, 64, 64, 600 2, 4, 4, 8, 2; , 2, 4, 8, 8 ; B, I, B, A, F, I, B, A, F, I, B, A, F, I, B, A, F, I, B, A, F; , F, F, F, F, F, B, A, F, F 80, 80, 80, 80, 80, 80; , 8080, 8080, 8080, 8080, 8080, 8080, 8080, 8080, 8080 6.30.01 - - - 0 kasson 0 vspg4
Re: 171.64.65.56 is in Reject status
Posted: Tue Oct 20, 2009 3:06 pm
by kasson
Server restarted. A simple sentence is usually sufficient rather than pasting a stats line. If I were a perl script, I'd be able to process serverstat directly.
