Cannot transmit to 171.64.65.111

Moderators: Site Moderators, FAHC Science Team

Post Reply
parkut
Posts: 363
Joined: Tue Feb 12, 2008 7:33 am
Hardware configuration: Running exclusively Linux headless blades. All are dedicated crunching machines.
Location: SE Michigan, USA

503 error on 171.67.108.17 and 171.64.65.111

Post by parkut »

Four different machines in my garden seem to have problems uploading... They have managed to get new work...

[00:49:08] - Autosending finished units...
[00:49:08] Trying to send all finished work units

[00:49:08] + Attempting to send results
[00:49:08] - Reading file work/wuresults_05.dat from core
[00:49:08] (Read 4202777 bytes from disk)
[00:49:08] Connecting to http://171.64.65.111:8080/
[00:49:11] - Couldn't send HTTP request to server
[00:49:11] (Got status 503)
[00:49:11] + Could not connect to Work Server (results)
[00:49:11] (171.64.65.111:8080)
[00:49:11] - Error: Could not transmit unit 05 (completed November 9) to work server.
[00:49:11] - 16 failed uploads of this unit.

[00:49:11] + Attempting to send results
[00:49:11] - Reading file work/wuresults_05.dat from core
[00:49:11] (Read 4202777 bytes from disk)
[00:49:11] Connecting to http://171.67.108.17:8080/
[00:49:15] - Couldn't send HTTP request to server
[00:49:15] (Got status 503)
[00:49:15] + Could not connect to Work Server (results)
[00:49:15] (171.67.108.17:8080)
[00:49:15] Could not transmit unit 05 to Collection server; keeping in queue.
[00:49:15] + Sent 0 of 1 completed units to the server
[00:49:15] - Autosend completed
Sahkuhnder
Posts: 43
Joined: Sun Dec 02, 2007 5:28 am
Location: Vegas Baby! Yeah!

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by Sahkuhnder »

I have been having the same problem for awhile now too.

171.64.65.111 has been in reject since very early Sunday morning.

When the WU is uploaded to any other server the "Server does not have record of this unit."

Be patient and hopefully the problem will be repaired soon. :|
Image
[BrainBug]
Posts: 24
Joined: Tue Oct 14, 2008 4:59 pm

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by [BrainBug] »

I also have 4 WU's that are awaiting upload :(
Last edited by [BrainBug] on Wed Nov 12, 2008 6:27 am, edited 2 times in total.
Image
jrabb1920
Posts: 7
Joined: Mon Dec 03, 2007 2:33 am

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by jrabb1920 »

Is this server still down, I have several work units that fail to go back to the collection server.
[BrainBug]
Posts: 24
Joined: Tue Oct 14, 2008 4:59 pm

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by [BrainBug] »

Both still down. :\ I hope they fix it soon.
Image
jrabb1920
Posts: 7
Joined: Mon Dec 03, 2007 2:33 am

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by jrabb1920 »

No one checking on this server, it would be nice if someone would at least tell us whats up with it, going on with about six work units waiting to get sent in.
Sahkuhnder
Posts: 43
Joined: Sun Dec 02, 2007 5:28 am
Location: Vegas Baby! Yeah!

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by Sahkuhnder »

I have completed WUs in the queues that have been trying to send for a couple days now too.

Code: Select all

[20:38:02] Completed 1375000 out of 2500000 steps  (55)
[20:39:56] Writing checkpoint files


[20:41:02] + Attempting to send results
[20:41:04] - Couldn't send HTTP request to server
[20:41:04] + Could not connect to Work Server (results)
[20:41:04]     (171.64.65.111:80)
[20:41:04] - Error: Could not transmit unit 06 (completed November 9) to work server.


[20:41:04] + Attempting to send results
[20:41:25] - Couldn't send HTTP request to server
[20:41:25] + Could not connect to Work Server (results)
[20:41:25]     (171.67.108.17:80)
[20:41:25]   Could not transmit unit 06 to Collection server; keeping in queue.
[20:42:56] Writing checkpoint files
[20:45:56] Writing checkpoint files
[20:48:56] Writing checkpoint files
[20:51:15] Writing local files
[20:51:15] Completed 1400000 out of 2500000 steps  (56)
Could someone please correct the problem? Thanks -
Image
[BrainBug]
Posts: 24
Joined: Tue Oct 14, 2008 4:59 pm

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by [BrainBug] »

Or at least provide a status report?
Image
birefringent
Posts: 13
Joined: Tue Jul 22, 2008 4:22 am

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by birefringent »

Same post, different thread. Just adding my voice to choir. 64 65 111
osgorth
Posts: 72
Joined: Fri Sep 12, 2008 10:46 am

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by osgorth »

Same here, now almost all my clients have 1 completed WU in store.. At least they're still crunching. :)
Image
edrutter
Posts: 2
Joined: Sat Dec 08, 2007 9:48 pm
Location: Baltimore MD

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by edrutter »

[BrainBug] wrote:Or at least provide a status report?

I agree, it just goes on,and on and on.If it can not accept finhised WU's why not shut the whole thing down untill it is fixed? Then we could work on WU's they want.
Ed Rutter
[BrainBug]
Posts: 24
Joined: Tue Oct 14, 2008 4:59 pm

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by [BrainBug] »

Somebody? Anybody?! Ugh!!!!!
Image
[BrainBug]
Posts: 24
Joined: Tue Oct 14, 2008 4:59 pm

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by [BrainBug] »

I STILL can't send 4 of the completed work units to EITHER of these IP's! Is this thread being ignored?
Image
Sahkuhnder
Posts: 43
Joined: Sun Dec 02, 2007 5:28 am
Location: Vegas Baby! Yeah!

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by Sahkuhnder »

171.64.65.111 has been in reject for four days now.

On the very rare occasion that the alternate at 171.67.108.17 accepts the WU the answer is always "Server has no record of this unit".

These are small WUs with correspondingly short deadlines. As nobody wants to see them expire and be lost could someone *please* fix the servers so that they will accept the WUs.
Image
jrabb1920
Posts: 7
Joined: Mon Dec 03, 2007 2:33 am

Re: 503 error on 171.67.108.17 and 171.64.65.111

Post by jrabb1920 »

I really can't believe that no one is looking into this, might as well turn the rigs off in tell they decide to do something about this, at least give us an answer in what is not being done on this, sorry I'm just a little bent that no one is answering this thread.
Post Reply