Page 2 of 4
Re: 128.59.74.4 in Reject
Posted: Fri Mar 06, 2009 5:00 am
by kelliegang
I understand that the collection servers are inundated at the moment but is this because of that?
Code: Select all
[23:03:08] + Attempting to send results [March 5 23:03:08 UTC]
[23:03:08] - Reading file work/wuresults_00.dat from core
[23:03:08] (Read 871464 bytes from disk)
[23:03:08] Connecting to http://171.65.103.100:8080/
[23:03:09] - Couldn't send HTTP request to server
[23:03:09] (Got status 503)
[23:03:09] + Could not connect to Work Server (results)
[23:03:09] (171.65.103.100:8080)
[23:03:09] + Retrying using alternative port
[23:03:09] Connecting to http://171.65.103.100:80/
[23:03:20] Posted data.
[23:03:21] Initial: 0000; - Server reports packet it received specified a data size of 0.
[23:03:21] (May be due to corruption during network transmission or a corrupted file.)
[23:03:21] Could not transmit unit 00 to Collection server; keeping in queue.
[23:03:21] + Sent 0 of 2 completed units to the server
[23:03:21] - Autosend completed
Re: 128.59.74.4 in Reject
Posted: Fri Mar 06, 2009 7:04 pm
by mrshirts
Latest update: another machine should be in place on Monday at Columbia, so I should be able to forward WU to a working server at that point. I'll post again on Monday with an update. Apologies for the inconvenience -- 128.59.74.4 will of course be retired, and things should work more smoothly here at U Va, since I'll be directly maintaining the machines.
Re: 128.59.74.4 in Reject
Posted: Sun Mar 08, 2009 6:34 pm
by Furiey
Thanks for the update, both my father and I have work units waiting to upload to this server.
Re: 128.59.74.4 in Reject
Posted: Tue Mar 10, 2009 12:33 pm
by mrshirts
The IT guy at Columbia has a backload, so the computer to relay the WU is not up yet. I'll keep updating as more information comes available. Since the timeout is long (60 days), hopefully most people will not end up affected in the end.
Error: Could not transmit unit 05 (completed February 25) to
Posted: Wed Mar 11, 2009 4:49 pm
by Nikos
This WU cant be uploaded. The WU's after this are uploaded ok.
What to do?
Username: Nik05
Code: Select all
[13:48:57] + Attempting to send results [March 11 13:48:57 UTC]
[13:48:57] Core found.
[13:48:58] Working on queue slot 08 [March 11 13:48:58 UTC]
[13:48:58] + Working ...
[13:48:58] - Couldn't send HTTP request to server
[13:48:58] + Could not connect to Work Server (results)
[13:48:58] (128.59.74.4:8080)
[13:48:58] + Retrying using alternative port
[13:48:58] - Couldn't send HTTP request to server
[13:48:58] + Could not connect to Work Server (results)
[13:48:58] (128.59.74.4:80)
[13:48:58] - Error: Could not transmit unit 05 (completed February 25) to work server.
[13:48:58] + Attempting to send results [March 11 13:48:58 UTC]
[13:48:58] - Couldn't send HTTP request to server
[13:48:58] + Could not connect to Work Server (results)
[13:48:58] (171.65.103.100:8080)
[13:48:58] + Retrying using alternative port
[13:48:58] - Couldn't send HTTP request to server
[13:48:58] + Could not connect to Work Server (results)
[13:48:58] (171.65.103.100:80)
[13:48:58] Could not transmit unit 05 to Collection server; keeping in queue.
Re: Error: Could not transmit unit 05 (completed February 25) to
Posted: Wed Mar 11, 2009 6:30 pm
by brityank
Nikos wrote:This WU cant be uploaded. The WU's after this are uploaded ok.
What to do?
Username: Nik05
Just have to wait until
mrshirts gets the server stable. The WU will stay in your queue and will retry every six hours, meanwhile your F@H program will continue working on newer WUs. Wait a week and then come back if it hasn't tripped out. Cheers.
Re: 128.59.74.4 in Reject
Posted: Thu Mar 12, 2009 11:12 am
by MDCRL
Thanks for the continued update of this server - I have two systems now waiting on it's return.
..... waiting patiently
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 4:18 am
by birefringent
I estimate as little as six more days before the buffer is overwritten. I know science isn't as important as me getting my points, or perhaps its the other way around. Either way the FAH console does set a time limit.
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 11:23 am
by toTOW
The queue entries won't be overwritten. The client will skip them and preserve the queued results.
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 8:19 pm
by ralgith
I'm also waiting on this one... weee..... Gotta love server issues
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 8:23 pm
by muziqaz
toTOW wrote:The queue entries won't be overwritten. The client will skip them and preserve the queued results.
but if the queue is full? and your finished WU gets rejected? then it overwrites queued WU in the first slot. Or at least that's my thought about that issue
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 10:01 pm
by mrshirts
Good news! Although we were not able to bring the machine up at Columbia, we set up another machine and I configured it to forward the traffic to the new Virginia machine. I can see the WU rolling in as I speak now. All the old data is preserved as well.
It will take a little bit longer to set it up so that the credits are properly put into the database automatically, because of this port forwarding, but we'll get it taken care off. At this point, the WU are being accepted, the stats files are being created, and they will be processed -- possibly it will take until Monday. But the major problem has been fixed.
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 10:06 pm
by kelliegang
WOOHOO!
Thanks for your diligence MrShirts!
Re: 128.59.74.4 in Reject
Posted: Fri Mar 13, 2009 10:24 pm
by muziqaz
thank you
Edit:
Still cannot connect. and retries to connect are very short.
can it be that I am trying to send my WUs through virtual pc? no firewalls, nothing. even router is in DMZ mode for my pc.
Re: 128.59.74.4 in Reject
Posted: Sat Mar 14, 2009 12:32 am
by Teddy
No luck uploading work units here, we'll check on the status of this tonight when I get home...
Teddy