It must be Friday...

nomad8u

[H]ard|DCer of the Month - December 2008
Joined
Feb 12, 2004
Messages
1,083
I don't even need a stinking calendar any more...

Code:
[13:34:25] + Attempting to send results [August 29 13:34:25 UTC]
[13:34:25] - Reading file work/wuresults_00.dat from core
[13:34:25]   (Read 1155148 bytes from disk)
[13:34:25] Connecting to http://171.64.65.106:8080/
[13:34:26] - Couldn't send HTTP request to server
[13:34:26] + Could not connect to Work Server (results)
[13:34:26]     (171.64.65.106:8080)
[13:34:26] + Retrying using alternative port
[13:34:26] Connecting to http://171.64.65.106:80/
[13:34:27] - Couldn't send HTTP request to server
[13:34:27] + Could not connect to Work Server (results)
[13:34:27]     (171.64.65.106:80)
[13:34:27] - Error: Could not transmit unit 00 (completed August 29) to work server.
[13:34:27] - 7 failed uploads of this unit.
[13:34:27] - Read packet limit of 540015616... Set to 524286976.


[13:34:27] + Attempting to send results [August 29 13:34:27 UTC]
[13:34:27] - Reading file work/wuresults_00.dat from core
[13:34:27]   (Read 1155148 bytes from disk)
[13:34:27] Connecting to http://171.64.122.76:8080/
[13:34:28] Will resume from checkpoint file
[13:34:28] - Couldn't send HTTP request to server
[13:34:28] + Could not connect to Work Server (results)
[13:34:28]     (171.64.122.76:8080)
[13:34:28] + Retrying using alternative port
[13:34:28] Connecting to http://171.64.122.76:80/
[13:34:28] - Couldn't send HTTP request to server
[13:34:28] + Could not connect to Work Server (results)
[13:34:28]     (171.64.122.76:80)
[13:34:28]   Could not transmit unit 00 to Collection server; keeping in queue.
[13:34:28] + Sent 0 of 2 completed units to the server

Primary collection server is down and the backup is yakking as well. Have 2 clients like this and yes I reported it at FCF but this is getting SOOOO old.

Just an informational rant.. :rolleyes:


 
Sweet. Something to look forward to. I've been down for the last 2 days because I don't have a UPS on my main rig (in the works) and I was away on business and now it's about to drop two and last weekend it took hours to get a new WU.

 
Glad I'm not the only one. :rolleyes:


216
 
I just checked back in @ FCF and Vijay must have kicked the server. It's back up now so if you've got some sitting around and want to flush them up just stop/restart the client and you should be good.... :cool:

I swear I don't understand how it's getting to be every weekend almost, starting on Friday morning. I could see the servers getting choked on the weekend if it was due to part time folders firing up clients but this has been the past 3 or 4 Friday mornings like clock work.

Weird.


 
Great. I had to reset my DSL when I got home yesterday so I lost many hours of production there, and now this. I hope mine is assigned to a non borked server. I will see when I get home in 7 hours I guess...

 
Same here, haven't been able to send all morning. At least I'm able to get work

If you have access to the box, check your log and see if it's the same server. If so, stopping and restarting the client will upload all the waiting WUs. If it's not the same server, report it here.


 
No, it's a friday before a long weekend. :)

I have no clue whats happening with the boxen with me being at work.

Now if I can just find someone to buy some of this bond I can get someone more folding hardware ;)
 
Oh man please o please don't start this for three damn days! I've just finally gotten my farm to 100% stabilize and had no reboots, heat issues or anything all week!

 
Knocking on some wood (real stuff, not my MDF desk), I seem to be ok. Unlike last weekend, my SMP & GPU2 clients seem to be ok.

Now my big concern is that people might be getting frustrated with the "outages" and not letting the SMP & GPU2 clients run on weekends because for the last couple of weekends, they have sat idle.

Obviously there are more than a few with dedicated farms, but the vast majority are still single SMP & GPU2 folders

 
Back
Top