Page 9 of 9

Re: Cannot send Work Unit to Server...

Posted: Sun Jan 10, 2010 4:03 pm
by Daniel0108
Okay, thanks!!! :)
I will try it when the server stat upgrade is done ;)
I will write then what happened :)
Thanks again :lol:
Daniel

Re: Cannot transmit to 171.64.65.111

Posted: Thu Mar 04, 2010 4:21 pm
by jtdc
For some reason I can't send to this server too as of this time. Stuck at

[16:15:07] + Attempting to send results [March 4 16:15:07 UTC]
[16:15:07] - Reading file work/wuresults_06.dat from core
[16:15:07] (Read 4833973 bytes from disk)
[16:15:07] Connecting to http://171.64.65.111:8080/

But all my internet connection going fine. I wonder, maybe some maintenance ongoing?

Re: Cannot transmit to 171.64.65.111

Posted: Fri Apr 02, 2010 4:12 pm
by AgrFan
171.64.65.111 is in REJECT .. unable to upload results or get new work .. P4 2.53ghz, Linux client 6.02, 768MB, big, advmethods.

Code: Select all

[15:53:42] + Attempting to send results
[15:53:42] - Couldn't send HTTP request to server
[15:53:42] + Could not connect to Work Server (results)
[15:53:42]     (171.64.65.111:8080)
[15:53:42] - Error: Could not transmit unit 09 (completed April 2) to work server.
[15:53:42]   Keeping unit 09 in queue.
[15:53:42] - Read packet limit of 540015616... Set to 524286976.


[15:53:42] + Attempting to send results
[15:53:42] - Couldn't send HTTP request to server
[15:53:42] + Could not connect to Work Server (results)
[15:53:42]     (171.64.65.111:8080)
[15:53:42] - Error: Could not transmit unit 09 (completed April 2) to work server.
[15:53:42] - Read packet limit of 540015616... Set to 524286976.


[15:53:42] + Attempting to send results
[15:53:42] - Couldn't send HTTP request to server
[15:53:42] + Could not connect to Work Server (results)
[15:53:42]     (171.67.108.17:8080)
[15:53:42]   Could not transmit unit 09 to Collection server; keeping in queue.
[15:53:42] - Preparing to get new work unit...
[15:53:42] + Attempting to get work packet
[15:53:42] - Connecting to assignment server
[15:53:43] + No appropriate work server was available; will try again in a bit.
[15:53:43] + Couldn't get work instructions.
[15:53:43] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[15:53:57] + Attempting to get work packet
[15:53:57] - Connecting to assignment server
[15:53:57] + No appropriate work server was available; will try again in a bit.
[15:53:57] + Couldn't get work instructions.
[15:53:57] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[15:54:12] + Attempting to get work packet
[15:54:12] - Connecting to assignment server
[15:54:12] + No appropriate work server was available; will try again in a bit.
[15:54:12] + Couldn't get work instructions.
[15:54:12] - Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[15:54:33] + Attempting to get work packet
[15:54:33] - Connecting to assignment server
[15:54:33] + No appropriate work server was available; will try again in a bit.
[15:54:33] + Couldn't get work instructions.
[15:54:33] - Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[15:55:22] + Attempting to get work packet
[15:55:22] - Connecting to assignment server
[15:55:23] + No appropriate work server was available; will try again in a bit.
[15:55:23] + Couldn't get work instructions.
[15:55:23] - Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.

Re: Cannot transmit to 171.64.65.111

Posted: Fri Apr 02, 2010 11:30 pm
by DrBB1
I have similar problem. Note Status 503. Server log says "Reject" for 171.64.65.111.

Code: Select all

23:02:56] + Processing work unit
[23:02:56] Project: 6313 (Run 667, Clone 6, Gen 24)
[23:02:56] - Read packet limit of 540015616... Set to 524286976.


[23:02:56] + Attempting to send results [April 2 23:02:56 UTC]
[23:02:56] Core required: FahCore_82.exe
[23:02:56] Core found.
[23:02:56] Working on queue slot 04 [April 2 23:02:56 UTC]
[23:02:56] + Working ...
[23:02:57] 
[23:02:57] *------------------------------*
[23:02:57] Folding@Home PMD Core
[23:02:57] Version 1.03 (September 7, 2005)
[23:02:57] 
[23:02:57] Preparing to commence simulation
[23:02:57] - Looking at optimizations...
[23:02:57] - Files status OK
[23:02:57] - Expanded 20751 -> 132134 (decompressed 636.7 percent)
[23:02:57] 
[23:02:57] Project: 4615 (Run 9, Clone 129, Gen 38)
[23:02:57] 
[23:02:57] Assembly optimizations on if available.
[23:02:57] Entering M.D.
[23:02:58] - Couldn't send HTTP request to server
[23:02:58] + Could not connect to Work Server (results)
[23:02:58]     (171.64.65.111:8080)
[23:02:58] + Retrying using alternative port
[23:02:59] - Couldn't send HTTP request to server
[23:02:59] + Could not connect to Work Server (results)
[23:02:59]     (171.64.65.111:80)
[23:02:59] - Error: Could not transmit unit 03 (completed April 2) to work server.
[23:02:59] - Read packet limit of 540015616... Set to 524286976.


[23:02:59] + Attempting to send results [April 2 23:02:59 UTC]
[23:02:59] - Couldn't send HTTP request to server
[23:02:59]   (Got status 503)
[23:02:59] + Could not connect to Work Server (results)
[23:02:59]     (171.67.108.17:8080)
[23:02:59] + Retrying using alternative port
[23:02:59] - Couldn't send HTTP request to server
[23:02:59]   (Got status 503)
[23:02:59] + Could not connect to Work Server (results)
[23:02:59]     (171.67.108.17:80)
[23:02:59]   Could not transmit unit 03 to Collection server; keeping in queue.

Re: Cannot transmit to 171.64.65.111

Posted: Sat Apr 03, 2010 1:12 am
by bruce
Yes, that server is currently down. The Pande Group is aware of the problem.

Re: Cannot transmit to 171.64.65.111

Posted: Sat Apr 03, 2010 9:19 am
by KroontjesPen
Having problems with the 129.74.85.48 start this problem also here.

Code: Select all

[02:23:30] Completed 495000 out of 500000 steps  (99%)
[02:31:56] Opening http://foldingforum.org/...
[02:32:50] Writing local files
[02:32:50] Completed 500000 out of 500000 steps  (100%)
[02:32:50] Writing final coordinates.
[02:32:50] Past main M.D. loop
[02:33:50] 
[02:33:50] Finished Work Unit:
[02:33:50] - Reading up to 362448 from "work/wudata_07.arc": Read 362448
[02:33:50] - Reading up to 3514816 from "work/wudata_07.xtc": Read 3514816
[02:33:50] goefile size: 0
[02:33:50] logfile size: 930019
[02:33:50] Leaving Run
[02:33:54] - Writing 6571575 bytes of core data to disk...
[02:33:55] Done: 6571063 -> 4730527 (compressed to 71.9 percent)
[02:33:55]   ... Done.
[02:33:55] - Shutting down core
[02:33:55] 
[02:33:55] Folding@home Core Shutdown: FINISHED_UNIT
[02:33:59] CoreStatus = 64 (100)
[02:33:59] Sending work to server
[02:33:59] Project: 6314 (Run 392, Clone 19, Gen 13)
[02:33:59] - Read packet limit of 540015616... Set to 524286976.


[02:33:59] + Attempting to send results [April 3 02:33:59 UTC]
[02:34:01] - Couldn't send HTTP request to server
[02:34:01] + Could not connect to Work Server (results)
[02:34:01]     (171.64.65.111:8080)
[02:34:01] + Retrying using alternative port
[02:34:02] - Couldn't send HTTP request to server
[02:34:02] + Could not connect to Work Server (results)
[02:34:02]     (171.64.65.111:80)
[02:34:02] - Error: Could not transmit unit 07 (completed April 3) to work server.
[02:34:02]   Keeping unit 07 in queue.
[02:34:02] Project: 6314 (Run 392, Clone 19, Gen 13)
[02:34:02] - Read packet limit of 540015616... Set to 524286976.


[02:34:02] + Attempting to send results [April 3 02:34:02 UTC]
[02:34:04] - Couldn't send HTTP request to server
[02:34:04] + Could not connect to Work Server (results)
[02:34:04]     (171.64.65.111:8080)
[02:34:04] + Retrying using alternative port
[02:34:05] - Couldn't send HTTP request to server
[02:34:05] + Could not connect to Work Server (results)
[02:34:05]     (171.64.65.111:80)
[02:34:05] - Error: Could not transmit unit 07 (completed April 3) to work server.
[02:34:05] - Read packet limit of 540015616... Set to 524286976.


[02:34:05] + Attempting to send results [April 3 02:34:05 UTC]
[07:07:06] + Could not connect to Work Server (results)
[07:07:06]     (171.67.108.17:8080)
[07:07:06] + Retrying using alternative port

Sorry I don't want to lose more work.
Again, I have no work on this PC so I shall restart the client and hope its working without losses.

Re: Cannot transmit to 171.64.65.111

Posted: Sat Apr 03, 2010 10:53 pm
by endrik
bruce wrote:Yes, that server is currently down. The Pande Group is aware of the problem.
171.64.65.11 is only half the problem - it happens. But what about the collection server 4 ? http://fah-web.stanford.edu/serverstat.html is showing normal operation, but I can't upload since yesterday:

Code: Select all

[22:43:32] Working on Unit 03 [April 3 22:43:32]
[22:43:34] + Could not connect to Work Server (results)
[22:43:34]     (171.64.65.111:8080)
[22:43:34] - Error: Could not transmit unit 02 to work server.

[22:43:34] + Attempting to send results
[22:43:35] - Couldn't send HTTP request to server
[22:43:35] + Could not connect to Work Server (results)
[22:43:35]     (171.67.108.17:8080)
[22:43:35]   Could not transmit unit 02 to Collection server; keeping in queue.

Re: Cannot transmit to 171.64.65.111

Posted: Sun Apr 04, 2010 8:05 pm
by noprob

Code: Select all

[20:55:19] - Machine ID: 1
[20:55:19] 
[20:55:20] Loaded queue successfully.
[20:55:20] Attempting to return result(s) to server...
[20:55:20] Trying to send all finished work units
[20:55:20] Project: 6316 (Run 492, Clone 9, Gen 35)


[20:55:20] + Attempting to send results [April 4 20:55:20 UTC]
[20:55:20] - Reading file work/wuresults_08.dat from core
[20:55:20]   (Read 4779799 bytes from disk)
[20:55:20] Connecting to http://171.64.65.111:8080/
[20:55:22] - Couldn't send HTTP request to server
[20:55:22] + Could not connect to Work Server (results)
[20:55:22]     (171.64.65.111:8080)
[20:55:22] + Retrying using alternative port
[20:55:22] Connecting to http://171.64.65.111:80/
[20:55:26] - Couldn't send HTTP request to server
[20:55:26] + Could not connect to Work Server (results)
[20:55:26]     (171.64.65.111:80)
[20:55:26] - Error: Could not transmit unit 08 (completed April 3) to work server.
[20:55:26] - 21 failed uploads of this unit.

Re: Cannot transmit to 171.64.65.111

Posted: Sun Apr 04, 2010 8:50 pm
by djohnston
I am having same problems since April 3rd.

Re: Cannot transmit to 171.64.65.111

Posted: Sun Apr 04, 2010 9:34 pm
by Teddy
Yep looks like 111 has been down for a few days now, have units banked up ready to be sent, guess much won't be done @ Easter.

Also got a standard client out of work as well, I guess if it can't return work it does not matter that it can't get any. So much for redundancy....
changing client configuration makes zero difference.
Other clients run without problems, it seems the classic client is less important or is that my perception?

Teddy

Re: Cannot transmit to 171.64.65.111

Posted: Sun Apr 04, 2010 11:08 pm
by hj47
I too am having trouble uploading a P6316 WU to this server :(

Re: Cannot transmit to 171.64.65.111

Posted: Wed Apr 21, 2010 2:23 pm
by _r2w_ben
Except for some brief uptime around Mon Apr 19 22:55:10 PDT (received 18 work units) and Tue Apr 20 09:45:11 PDT (received 135 work units), 171.64.65.111 has been in Reject since Mon Apr 19 15:35:10 PDT.

The good news is I obtained new work from another server.