130.237.232.237 going down for maintenance

[csm725]

I use Langouste and am experiencing this issue with a 6903. Should I leave the machine idling? Will the WU upload (and will I download a new one) automatically when the server works again?

[kasson]

The server had an issue this morning, compounding the diagnostic uncertainty for these other questions. We anticipate it should be back up within an hour.

[csm725]

Thanks for the prompt response, Kasson. Appreciated.

[Nathan_P]

I use Langouste and am experiencing this issue with a 6903. Should I leave the machine idling? Will the WU upload (and will I download a new one) automatically when the server works again?

Possibly - possibly not, personally i would go into the Langouste folder and copy the file back to your main work directory,stop the client and restart it with the -sendall switch, that should do it. This is one of those times where langouste isn't much help ( it cost me a WU once so i stopped using it and take the small ppd hit instead). I would wait though until kasson confirms that the server is back up

[csm725]

After 4 tries of connecting to 130.237.232.237, I downloaded a 6097. I will let the rig fold overnight and I assume it'll pick a bigadv WU up when the server is back up.

[Biffa]

Is this server still having upload issues? I'm having trouble with a single 6903

Also noted that the server client type is set to classic from here http://fah-web.stanford.edu/serverstat.html was that the issue before?

FWIW this is direct from client with no proxy (langouste or otherwise)

Have tried changing MAchine ID

Code: Select all

--- Opening Log file [April 26 08:46:02 UTC] 


# Linux SMP Console Edition ###################################################
###############################################################################

                       Folding@Home Client Version 6.34

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /home/Biffa/fah
Executable: ./fah6
Arguments: -send all -verbosity 9 -smp 48 -bigadv -verbosity 9 -forceasm 

[08:46:02] - Ask before connecting: No
[08:46:02] - User name: Biffa (Team 10)
[08:46:02] - User ID: 1080DCA737FA22D9
[08:46:02] - Machine ID: 1
[08:46:02] 
[08:46:02] Loaded queue successfully.
[08:46:02] Attempting to return result(s) to server...
[08:46:02] Trying to send all finished work units
[08:46:02] Project: 6903 (Run 1, Clone 14, Gen 84)


[08:46:02] + Attempting to send results [April 26 08:46:02 UTC]
[08:46:02] - Reading file work/wuresults_02.dat from core
[08:46:03]   (Read 222415734 bytes from disk)
[08:46:03] Connecting to http://130.237.232.237:8080/
[08:53:17] - Couldn't send HTTP request to server
[08:53:17] + Could not connect to Work Server (results)
[08:53:17]     (130.237.232.237:8080)
[08:53:17] + Retrying using alternative port
[08:53:17] Connecting to http://130.237.232.237:80/
[08:56:37] - Couldn't send HTTP request to server
[08:56:37] + Could not connect to Work Server (results)
[08:56:37]     (130.237.232.237:80)
[08:56:37] - Error: Could not transmit unit 02 (completed April 25) to work server.
[08:56:37] - 7 failed uploads of this unit.
[08:56:37]   Keeping unit 02 in queue.
[08:56:37] + Sent 0 of 1 completed units to the server
[08:56:37] - Failed to send all units to server
[08:56:37] ***** Got a SIGTERM signal (15)
[08:56:37] Killing all core threads

Folding@Home Client Shutdown.

[Biffa]

Got another one that won't upload to this server now

Gonna miss the deadline for these Wu's at this stage.

[Biffa]

Uploads working again.

[dubzhouse]

I am still having issues uploading a wu that was completed four days ago to this server. I am able to get a new wu but unable to upload to this server or another server.
Any ideas on what could be causing this. I keep getting unable to connect to server.

[Grandpa_01]

Somebody need to go kick this server it has a 94% net load and is handing out the 511 byte WU's 1 right after the other. My Gulfies are having a gay old time trying to send and receive work.

[KMac]

It will also not successfully accept a completed 8101 work unit if you manage to avoid a 512 byte WU.

[kasson]

This server has been having issues. 8101 is on a different and more reliable server; we will direct most traffic to that instead.

[ei57]

Any idea when these issues will be adressed?

[bruce]

Any idea when these issues will be adressed?

You've been around the forum long enough to know Stanford doesn't make predictions. The standard answer to a "when" question is one of three possible answers: 1) "Not soon" or 2) "Soon" or 3) It's already fixed.

You already know they're working on the problem. If this is like most problems, almost all of the time to fix it is spent diagnosing the exact nature of the problem; once they know exactly what is causing the problem, fixing it is probably quite easy. If the exact cause of the problem is not known yet, no estimate can be given. (Yes, there are some exceptions).

If you read back through this topic, you already know that several potential fixes have already been tried and the problem is still there, so it's not going to be easy to fix.

Putting 8101 is on a different and more reliable server and redirecting assignment requests to that server is at least a case of "it's already fixed" though there's still work to needs to be done that's no longer critical.