No appropriate work server was available

Dev Hardware Forums Sponsor:

Trader Rating: 0 · #1

September 11th, 2008, 10:59 PM

fishtoprecords

Contributing User

Join Date: Aug 2008

Posts: 44

Folding Points: 2561127 Folding Title: Super Ultimate Folder - Level 6

Time spent in forums: 5 h 8 m 32 sec
Reputation Power: 620

No appropriate work server was available

My dual CPU system is not finding any work. I don't see much in the way of useful error logging. I can't tell if the stanford server is down, or I'm not resolving it, can't reach it, etc.?

Hints?

Code:

[03:57:33] + No appropriate work server was available; will try again in a bit.
[03:57:33] + Couldn't get work instructions.
[03:57:33] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[03:57:39] + Attempting to get work packet
[03:57:39] - Connecting to assignment server
[03:57:39] + No appropriate work server was available; will try again in a bit.
[03:57:39] + Couldn't get work instructions.
[03:57:39] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[03:57:44] + Attempting to get work packet
[03:57:44] - Connecting to assignment server

Trader Rating: 0 · #2

September 11th, 2008, 11:14 PM

fishtoprecords

Contributing User

Join Date: Aug 2008

Posts: 44

Time spent in forums: 5 h 8 m 32 sec
Reputation Power: 620

Ran the Java applet test, looks good to me. Here is the output

Code:

TCP/Web100 Network Diagnostic Tool v5.4.12
click START to begin
Connected to: iperf.stanford.edu  --  Using IPv4 address
Another client is currently being served, your test will begin within 45 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
checking for firewalls . . . . . . . . . . . . . . . . . . .  Done
running 10s outbound test (client-to-server [C2S]) . . . . . 2.48Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 748.61kb/s
The slowest link in the end-to-end path is a 10 Mbps Ethernet subnet
Information: Other network traffic is congesting the link
 [C2S]: Packet queuing detected
 [S2C]: Packet queuing detected

click START to re-test

I have no idea where the "other network traffic" may be that is "congesting the link" Doesn't seem to be between me and my ISP. Perhaps out near Stanford?

Trader Rating: 0 · #3

September 13th, 2008, 12:23 PM

screwballl

Contributing User

Join Date: Mar 2006

Location: NWFL

Posts: 412

Folding Points: 1419152 Folding Title: Super Ultimate Folder - Level 3

Time spent in forums: 2 Days 14 h 13 m 44 sec
Reputation Power: 2017

this is normal for stanford... there may be times where you see that message for 5 minutes... and sometimes when it is seen for 5 hours or longer... it is usually not dependent on your connection but the Stanford servers.

__________________

Click here for my rig specs

E6600 under Tt Big Typhoon on Gigabyte GA-EP35-DS3P with 4GB DDR2-800 OCZ
512MB 9800GT video and XFi XtremeMusic sound
Hard drives (all SATA):
500GB WD (backup, in external case),
320GB Seagate 7200.10 (XP Pro),
120GB WD server hard drive (Kubuntu with KDE 4.1)...
Multi-boot system
Corsair HX620W modular PSU
FOR SALE: 320MB evga 8800GTS

Everytime a mustache is shaved, an angel dies.

Trader Rating: 0 · #4

September 13th, 2008, 12:29 PM

fishtoprecords

Contributing User

Join Date: Aug 2008

Posts: 44

Time spent in forums: 5 h 8 m 32 sec
Reputation Power: 620

Quote:

Originally Posted by screwballl

this is normal for stanford... there may be times where you see that message for 5 minutes... and sometimes when it is seen for 5 hours or longer..

Thanks, I got it for several hours this time. Cleared itself up.

No appropriate work server was available

Developer Shed Affiliates