Page 1 of 1
171.67.108.60 Full/not accepting
Posted: Wed Mar 06, 2013 1:20 pm
by drougnor
Code: Select all
Waiting before retry.
[13:02:58] + Attempting to get work packet
[13:02:58] Passkey found
[13:02:58] - Will indicate memory of 3240 MB
[13:02:58] - Connecting to assignment server
[13:02:58] Connecting to http://assign.stanford.edu:8080/
[13:02:58] Posted data.
[13:02:58] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[13:02:58] + News From Folding@Home: Welcome to Folding@Home
[13:02:59] Loaded queue successfully.
[13:02:59] Sent data
[13:02:59] Connecting to http://171.67.108.60:8080/
[13:03:00] - Couldn't send HTTP request to server
[13:03:00] + Could not connect to Work Server
And per the Server Stats site -
Code: Select all
89 171.67.108.60 vsp12c shukla SMP full Reject 4.09 0 0 554 -168 18971 18971 18971 154 33 219 1 1 0 0 -_10000_I_80; WL_10000_A_80; WL_10000_B_80; WL_10000_F_80; WL_10000_A_80; WL_10000_B_80; WL_10000_F_80; X_10000_A_80; X_10000_B_80; X_10000_F_80; WL_10000_A_8080; WL_10000_B_8080; WL_10000_F_8080; WL_10000_F_8080; WL_10000_A_8080; WL_10000_B_8080; WL_10000_F_8080; WL_10000_B_8080; X_10000_A_8080; X_10000_B_8080; X_10000_F_8080
Re: 171.67.108.60 Full/not accepting
Posted: Thu Mar 07, 2013 1:57 am
by bruce
The server owner has been notified.
It seems to be switching between REJECT and ACCEPTING quite frequently so you might get through at any time.
Re: 171.67.108.60 Full/not accepting
Posted: Thu Mar 07, 2013 3:24 pm
by patonb
Mine switched to 171.64.65.75 to upload, but now I'm getting new errors
Code: Select all
15:17:33:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:35:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:37:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:40:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:42:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:45:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:47:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:49:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:52:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:54:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:56:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:17:59:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:01:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:04:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:06:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:08:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:11:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:13:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:15:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:18:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:20:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:23:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:25:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:27:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:30:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:32:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:34:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:37:21:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:39:24:127.0.0.1 GET /api/updates?sid=0xd79b728cb0da9c93333f48ec1d1eac9a
15:18:41:WARNING:Exception: 21:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
15:18:44:WARNING:Exception: 24:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
15:19:59:Started thread 21 on PID 2088
15:20:05:FS01:Paused
So I paused it.
Re: 171.67.108.60 Full/not accepting
Posted: Thu Mar 07, 2013 3:51 pm
by Jesse_V
That's not an error, it's a log of the communication between Web Control and FAHClient. Usually those AJAX requests are ony visible when verbosity is turned up above normal. The warnings at the bottom show that you closed Web Control, and the browser shut down that end of the communication in an unclean manner, which is also normal. Feel free to resume folding.
Re: 171.67.108.60 Full/not accepting
Posted: Thu Mar 07, 2013 7:47 pm
by patonb
I did after rebooting, but it sat there doing that, and didn't want to get a ddos ban.
Re: 171.67.108.60 Full/not accepting
Posted: Thu Mar 07, 2013 8:10 pm
by Jesse_V
patonb wrote:I did after rebooting, but it sat there doing that, and didn't want to get a ddos ban.
Sorry for not clarifying, but those communications are local with your own computer. They do not go out to the server. Web Control is communicating with the FAHClient software on your own computer, not anywhere else. So everything you posted in that log relates to your own system. See
http://folding.stanford.edu/English/V7- ... iate#ntoc2
Re: 171.67.108.60 Full/not accepting
Posted: Thu Mar 07, 2013 9:14 pm
by P5-133XL
If you would like to remove the gets from the log try changing the verbosity setting from 5 to the default 3.
Re: 171.67.108.60 Full/not accepting
Posted: Fri Mar 08, 2013 5:07 pm
by patonb
Oh yha I have verbosity 5 to get all the info incase there is an issue.
I had not seen that before and it came up right after the reject/accept so I decided to see if it was an issue.
Re: 171.67.108.60 Full/not accepting
Posted: Fri Mar 08, 2013 6:28 pm
by Joe_H
The extra information from verbosity 5 is rarely useful with the V7 client. In fact it often gets in the way of troubleshooting as it displays a large batch of default settings. Verbosity 3 is recommended for that reason as it shows everything that has been changed from default settings.
Re: 171.67.108.60 Full/not accepting
Posted: Fri Mar 08, 2013 7:13 pm
by patonb
Hmm, whcich verbosity is like the old 9 in v6?
The eason I switched to 5 was I find lacking in v7 logs are dates. As in the date it d/ls or uploads. So was hoping verb 5 gave more info.
Re: 171.67.108.60 Full/not accepting
Posted: Fri Mar 08, 2013 8:06 pm
by TheWolf
Perhaps I should have said the collection server in my last post.
Here is the log from another rig that's unable to send or get new work.
At the moment I have 3 rigs setting idle because they can't send or get new work.
Edit: update a stop of those clients and a restart has allowed then to get new work.
Still hasn't send in the work that's finished on a couple. I'll give it a while to see if those send.
Code: Select all
[18:48:04] Project: 8080 (Run 19, Clone 53, Gen 5)
[18:48:04] + Attempting to send results [March 8 18:48:04 UTC]
[18:48:05] - Couldn't send HTTP request to server
[18:48:05] + Could not connect to Work Server (results)
[18:48:05] (171.67.108.60:8080)
[18:48:05] + Retrying using alternative port
[18:48:07] - Couldn't send HTTP request to server
[18:48:07] + Could not connect to Work Server (results)
[18:48:07] (171.67.108.60:80)
[18:48:07] - Error: Could not transmit unit 05 (completed March 8) to work server.
[18:48:07] Keeping unit 05 in queue.
[18:48:07] Project: 8080 (Run 19, Clone 53, Gen 5)
[18:48:07] + Attempting to send results [March 8 18:48:07 UTC]
[18:48:08] - Couldn't send HTTP request to server
[18:48:08] + Could not connect to Work Server (results)
[18:48:08] (171.67.108.60:8080)
[18:48:08] + Retrying using alternative port
[18:48:09] - Couldn't send HTTP request to server
[18:48:09] + Could not connect to Work Server (results)
[18:48:09] (171.67.108.60:80)
[18:48:09] - Error: Could not transmit unit 05 (completed March 8) to work server.
[18:48:09] + Attempting to send results [March 8 18:48:09 UTC]
[18:48:39] + Results successfully sent
[18:48:39] Thank you for your contribution to Folding@Home.
[18:48:39] + Number of Units Completed: 349
[18:48:39] Successfully sent unit 05 to Collection server.
[18:48:39] - Preparing to get new work unit...
[18:48:39] Cleaning up work directory
[18:48:39] + Attempting to get work packet
[18:48:39] Passkey found
[18:48:39] - Connecting to assignment server
[18:48:40] - Successful: assigned to (128.143.199.96).
[18:48:40] + News From Folding@Home: Welcome to Folding@Home
[18:48:40] Loaded queue successfully.
[18:49:01] - Couldn't send HTTP request to server
[18:49:01] + Could not connect to Work Server
[18:49:01] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:49:13] + Attempting to get work packet
[18:49:13] Passkey found
[18:49:13] - Connecting to assignment server
[18:49:13] - Successful: assigned to (128.143.199.96).
[18:49:13] + News From Folding@Home: Welcome to Folding@Home
[18:49:14] Loaded queue successfully.
[18:49:35] - Couldn't send HTTP request to server
[18:49:35] + Could not connect to Work Server
[18:49:35] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[18:49:54] + Attempting to get work packet
[18:49:54] Passkey found
[18:49:54] - Connecting to assignment server
[18:49:54] - Successful: assigned to (128.143.199.96).
[18:49:54] + News From Folding@Home: Welcome to Folding@Home
[18:49:55] Loaded queue successfully.
[18:50:16] - Couldn't send HTTP request to server
[18:50:16] + Could not connect to Work Server
[18:50:16] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[18:50:50] + Attempting to get work packet
[18:50:50] Passkey found
[18:50:50] - Connecting to assignment server
[18:50:51] - Successful: assigned to (128.143.199.96).
[18:50:51] + News From Folding@Home: Welcome to Folding@Home
[18:50:51] Loaded queue successfully.
[18:51:12] - Couldn't send HTTP request to server
[18:51:12] + Could not connect to Work Server
[18:51:12] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[18:51:55] + Attempting to get work packet
[18:51:55] Passkey found
[18:51:55] - Connecting to assignment server
[18:51:55] - Successful: assigned to (128.143.199.96).
[18:51:55] + News From Folding@Home: Welcome to Folding@Home
[18:51:56] Loaded queue successfully.
[18:52:17] - Couldn't send HTTP request to server
[18:52:17] + Could not connect to Work Server
[18:52:17] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[18:53:45] + Attempting to get work packet
[18:53:45] Passkey found
[18:53:45] - Connecting to assignment server
[18:53:46] - Successful: assigned to (128.143.199.96).
[18:53:46] + News From Folding@Home: Welcome to Folding@Home
[18:53:46] Loaded queue successfully.
[18:54:07] - Couldn't send HTTP request to server
[18:54:07] + Could not connect to Work Server
[18:54:07] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[18:56:54] + Attempting to get work packet
[18:56:54] Passkey found
[18:56:54] - Connecting to assignment server
[18:56:55] - Successful: assigned to (128.143.199.96).
[18:56:55] + News From Folding@Home: Welcome to Folding@Home
[18:56:55] Loaded queue successfully.
[18:57:16] - Couldn't send HTTP request to server
[18:57:16] + Could not connect to Work Server
[18:57:16] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[19:02:37] + Attempting to get work packet
[19:02:37] Passkey found
[19:02:37] - Connecting to assignment server
[19:02:38] - Successful: assigned to (128.143.231.202).
[19:02:38] + News From Folding@Home: Welcome to Folding@Home
[19:02:38] Loaded queue successfully.
[19:06:24] + Could not connect to Work Server
[19:06:24] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[19:17:06] + Attempting to get work packet
[19:17:06] Passkey found
[19:17:06] - Connecting to assignment server
[19:17:07] - Successful: assigned to (128.143.231.202).
[19:17:07] + News From Folding@Home: Welcome to Folding@Home
[19:17:07] Loaded queue successfully.
[19:21:26] + Could not connect to Work Server
[19:21:26] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[19:42:49] + Attempting to get work packet
[19:42:49] Passkey found
[19:42:49] - Connecting to assignment server
[19:42:49] - Successful: assigned to (128.143.231.202).
[19:42:49] + News From Folding@Home: Welcome to Folding@Home
[19:42:49] Loaded queue successfully.
Re: 171.67.108.60 Full/not accepting
Posted: Fri Mar 08, 2013 8:09 pm
by Joe_H
patonb wrote:Hmm, whcich verbosity is like the old 9 in v6?
The eason I switched to 5 was I find lacking in v7 logs are dates. As in the date it d/ls or uploads. So was hoping verb 5 gave more info.
The V7 log places a date stamp in the log every 6 hours by default, you can modify that setting using the Expert level if that is not often enough. With the time stamps on every line that was considered often enough. Is there other information you would like to see in the log?
Re: 171.67.108.60 Full/not accepting
Posted: Fri Mar 08, 2013 8:52 pm
by Joe_H
TheWolf wrote:Perhaps I should have said the collection server in my last post.
Here is the log from another rig that's unable to send or get new work.
At the moment I have 3 rigs setting idle because they can't send or get new work.
Edit: update a stop of those clients and a restart has allowed then to get new work.
Still hasn't send in the work that's finished on a couple. I'll give it a while to see if those send.
171.67.108.60 has been having intermittent problems with connections, Some work has been migrated off this WS over the past few months for that reason. Sometimes it takes a while for the AS to move requests to a different WS or for an upload to switch to the CS if one is available. As for the uploads, if they don't send in a while post in the appropriate topic for that server IP.