Panic Mode On (78) Server Problems?

Whoa there, kibbles........
Down about 100K tasks since the bandwidth got tied tight.

And that's with 9 kitties asking for kibble every chance they get.

Kibble bowls still full here, but begeejus.

Trouble in kibble land.
____________
******

"Ask not, what your kitty can do for you. Ask what you can do for your kitty."

As it is kitten, so shall it be done.

That's good for you msattler but the last time I got tasks actually downloaded to my cruncher was over a day ago. Sure I've got a load of new tasks assigned to me but they are "ghosts", server assigned but not actually downloaded.

Thanks for looking. I have tried the no new task option twice and they are still showing in my tasks window. I understand we have a problem getting work units. I have my preferences set to take any type work unit. I am still not getting units. Is the work scheduler down or we just out of units?

I've aborted 6 AP task downloads. Each after they repeatedly tried to download never getting past the 1.5 KBps threshold and never past the 1.6% total down after an hour of logged download time. Got two spinning right now doing the same thing. I'd love to crunch these things, but if they never arrive I can't. Currently one of them has reached the 1.99% after 47 minutes (a new record!). If these need to be aborted as well, then I'll have to turn off AP downloads altogether until this is addressed.

I have noticed that there seems to be some relation to the transient HTTP error as each time the DL has stopped that error pops up in the log. There is no relation to reporting or uploading as I haven't crunched any type of work unit since (I think) Wednesday.

Well, just rebooted both the firewall and router and it shot up to 39 KBps and that rapidly dwindled to 3KBps. using the hosts method and declaring .21 as the go to server. tracert to both .21 and .13 reveal the transfer at berkeley is choked at 208.178.58.185 (unknown ownership) and 67.16.134.26 (a global exchange server)

[edit] After another timeout I ran another set of tracert: 64.71.140.42 didn't want to identify itself after having decent sub 20ms pings, 208.68.243.254 with 2 drops and a 59ms ping, 208.68.240.13 two lines with one dropped ping each and an average of 60ms.

[edit2] Seems to have sorted as I just got 4 AP units after aborting the two that were hanging.

Just for info .. - because it was asked.

I sent an EMail to the S@h admins Dave, Eric, Matt and Jeff at Friday Nov/02 01:08 UTC.

To now no answer.

For a few minutes I sent a 2nd EMail.


* Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *
____________


>Das Deutsche Cafe. The German Cafe.<

Just for info .. - because it was asked.

I sent an EMail to the S@h admins Dave, Eric, Matt and Jeff at Friday Nov/02 01:08 UTC.

To now no answer.

For a few minutes I sent a 2nd EMail.


* Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

Nothing to do with shorties, or APs. There's a problem with the scheduler which has been going on for a few weeks, even when there are few shorties or APs around. For some reason or other the scheduler just stops responding correctly for a few hours at a time, then crawls back into life for a bit, only to go off for anther nap. Very frustrating to put it mildly.
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Still crunching......
But many rigs are on their 2 and 3 hour comms timeouts.......not pretty.

Something other than just bandwidth saturation is at play here. And it's not playing well with others.
____________
******

"Ask not, what your kitty can do for you. Ask what you can do for your kitty."

As it is kitten, so shall it be done.