Jeff Cobb has posted an update for our woes in the HE thread
http://setiathome.berkeley.edu/forum_thread.php?id=64652&nowrap=true#1157929

cricket graph seems to be coming back to life. Whoever Jeff kicked, bribed or sweet talked to sort out the connection issues seems to have done the trick

If I was Admin in this situation, I would be completely incoherent. These are times that Sadms live on Cheeto's and Mountain Dew.

---

Janice

If I was Admin in this situation, I would be completely incoherent. These are times that Sadms live on Cheeto's and Mountain Dew.

and dessert is a heaping mound of Mento's :)

---

If I was Admin in this situation, I would be completely incoherent. These are times that Sadms live on Cheeto's and Mountain Dew.

and dessert is a heaping mound of Mento's :)

Mountain Dew Code Red or Voltage (Blue), microwave pizza snacks, and Hershey's miniatures (Ghirardeli when I can get them) or Reece's pieces. (8{)

---

Donald
Infernal Optimist / Submariner, retired

If I was Admin in this situation, I would be completely incoherent. These are times that Sadms live on Cheeto's and Mountain Dew.

and dessert is a heaping mound of Mento's :)

Mountain Dew Code Red or Voltage (Blue), microwave pizza snacks, and Hershey's miniatures (Ghirardeli when I can get them) or Reece's pieces. (8{)

Jumbo bag of Skittles. Pretty much pure sugar with some flavoring.

---

Something(s) definately stuffed.
Outbound network traffic is barely peaking at 60Mb/s, for a while there it wasn't even peaking at 30Mb/s. This is with both of my machines not having reached the present limits. One of them actually ran out of work because the upload server was down at one stage, and the backoffs from that resulted in it backing off for over 4 hours. At the moment it's backed off for over 6 hours due to the problem with the Scheduler.
Most requests to the Scheduler result in "project has no tasks available", which is odd considering the very low level of network traffic. When it does connect, it gets 2-3 tasks (DCF of 1.2).
However at the present moment all attempts to contect the Scheduler result in failure.

2/10/2011 8:57:30 SETI@home Sending scheduler request: To fetch work.
2/10/2011 8:57:30 SETI@home Reporting 6 completed tasks, requesting new tasks for CPU and GPU
2/10/2011 8:57:52 Project communication failed: attempting access to reference site
2/10/2011 8:57:52 SETI@home Scheduler request failed: Couldn't connect to server
2/10/2011 8:57:54 Internet access OK - project servers may be temporarily down.

and repeat time & time again.

---

Grant
Darwin NT

Something(s) definately stuffed.
Outbound network traffic is barely peaking at 60Mb/s, for a while there it wasn't even peaking at 30Mb/s. This is with both of my machines not having reached the present limits. One of them actually ran out of work because the upload server was down at one stage, and the backoffs from that resulted in it backing off for over 4 hours. At the moment it's backed off for over 6 hours due to the problem with the Scheduler.
Most requests to the Scheduler result in "project has no tasks available", which is odd considering the very low level of network traffic. When it does connect, it gets 2-3 tasks (DCF of 1.2).
However at the present moment all attempts to contect the Scheduler result in failure.

2/10/2011 8:57:30 SETI@home Sending scheduler request: To fetch work.
2/10/2011 8:57:30 SETI@home Reporting 6 completed tasks, requesting new tasks for CPU and GPU
2/10/2011 8:57:52 Project communication failed: attempting access to reference site
2/10/2011 8:57:52 SETI@home Scheduler request failed: Couldn't connect to server
2/10/2011 8:57:54 Internet access OK - project servers may be temporarily down.

and repeat time & time again.

The same here yet all tracerts and pings get through to all 4 IP's.

Cheers.

---

Claggy,

I am not on HE, and I have not received any GPU work since the last outage. Are they not splitting any?

I am only set up to request GPU's...

---

Team,

This following messages are typical today...

10/1/2011 7:40:19 PM | SETI@home | update requested by user
10/1/2011 7:40:21 PM | SETI@home | Sending scheduler request: Requested by user.
10/1/2011 7:40:21 PM | SETI@home | Requesting new tasks for NVIDIA GPU
10/1/2011 7:40:25 PM | SETI@home | Scheduler request completed: got 0 new tasks
10/1/2011 7:40:25 PM | SETI@home | No tasks sent
10/1/2011 7:40:25 PM | SETI@home | No tasks are available for SETI@home Enhanced
10/1/2011 7:40:25 PM | SETI@home | Tasks for CPU are available, but your preferences are set to not accept them


Jeff

---

10/1/2011 5:42:01 PM SETI@home Sending scheduler request: To fetch work.
10/1/2011 5:42:01 PM SETI@home Requesting new tasks for GPU
10/1/2011 5:42:43 PM SETI@home Scheduler request failed: HTTP internal server error

I get these to break the monotony

---

Janice

Team,

This following messages are typical today...

10/1/2011 7:40:19 PM | SETI@home | update requested by user
10/1/2011 7:40:21 PM | SETI@home | Sending scheduler request: Requested by user.
10/1/2011 7:40:21 PM | SETI@home | Requesting new tasks for NVIDIA GPU
10/1/2011 7:40:25 PM | SETI@home | Scheduler request completed: got 0 new tasks
10/1/2011 7:40:25 PM | SETI@home | No tasks sent
10/1/2011 7:40:25 PM | SETI@home | No tasks are available for SETI@home Enhanced
10/1/2011 7:40:25 PM | SETI@home | Tasks for CPU are available, but your preferences are set to not accept them


Jeff

I wonder if that means that there's a lot of VLAR's around, (VLAR's aren't sent to Nvidia GPU's)

Claggy

So.. I keep hearing about this limit of 50/cpu... my single core machine has 99 in progress and the messages tab says nothing about a limit. Hm. Now it's 100, still no message. Either it's a glitch, or it's because a 10-day cache on this machine is somewhere between 90-110 MBs on average, at least with the weird estimates and most of them being shorties.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)