I started getting this message yesterday
"Access to referance site succeeded - project servers may be temporarily down".

Checked servers, closed pc down overnight, this morning, same message.

cant find any info on a problem, anyone else having a prob or should it correct itself?

Thanks ;0)

---

Ok, just seen that I am not the only one with this problem,

guess we have to wait

---

I had some downloads hanging yesterday.

But it has cleared out now.
09.06.2007 09:44:49|SETI@home|Starting task 15mr05aa.455.24497.1047168.3.111_1 using setiathome_enhanced version 517
09.06.2007 09:44:51|SETI@home|[file_xfer] Started upload of file 15mr05aa.455.23696.334664.3.31_1_0
09.06.2007 09:44:59|SETI@home|[file_xfer] Finished upload of file 15mr05aa.455.23696.334664.3.31_1_0
09.06.2007 09:44:59|SETI@home|[file_xfer] Throughput 4669 bytes/sec
09.06.2007 09:45:03|SETI@home|Sending scheduler request: To report completed tasks
09.06.2007 09:45:03|SETI@home|Reporting 1 tasks
09.06.2007 09:45:13|SETI@home|Scheduler RPC succeeded [server version 509]
09.06.2007 09:45:13|SETI@home|Deferring communication 11 sec, because requested by project
09.06.2007 10:02:17|SETI@home|Task 15mr05aa.7904.18528.597160.3.55_2 exited with zero status but no 'finished' file
09.06.2007 10:02:17|SETI@home|If this happens repeatedly you may need to reset the project.
09.06.2007 10:02:17|SETI@home|Restarting task 15mr05aa.7904.18528.597160.3.55_2 using setiathome_enhanced version 517
09.06.2007 11:22:49|SETI@home|Computation for task 15mr05aa.7904.18528.597160.3.55_2 finished
09.06.2007 11:22:49||Starting 04mr05aa.15309.8242.915908.3.54_3
09.06.2007 11:22:51|SETI@home|Starting task 04mr05aa.15309.8242.915908.3.54_3 using setiathome_enhanced version 517
09.06.2007 11:22:52|SETI@home|[file_xfer] Started upload of file 15mr05aa.7904.18528.597160.3.55_2_0
09.06.2007 11:22:58|SETI@home|[file_xfer] Finished upload of file 15mr05aa.7904.18528.597160.3.55_2_0
09.06.2007 11:22:58|SETI@home|[file_xfer] Throughput 7707 bytes/sec
09.06.2007 11:23:03|SETI@home|Sending scheduler request: To report completed tasks
09.06.2007 11:23:03|SETI@home|Reporting 1 tasks
09.06.2007 11:23:14|SETI@home|Scheduler RPC succeeded [server version 509]
09.06.2007 11:23:14|SETI@home|Deferring communication 11 sec, because requested by project

Mike

---

With each crime and every kindness we birth our future.

The Cricket graph just nose-dived.

They seems down to me, can upload, but not report. Try again later I guess.

The Cricket graph just nose-dived.

I got fooled by the Server Status page being all "Green". Then I realized the last update was:

[As of 8 Jun 2007 21:00:14 UTC]

---

Yup....getting HTTP internal server errors trying to report completed work. Uploads seem to still be working OK.
The Cricket graph has bombed, and even server response on these forums is real laggy.
Sumpthin's gone away.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Yup....getting HTTP internal server errors trying to report completed work. Uploads seem to still be working OK.
The Cricket graph has bombed, and even server response on these forums is real laggy.
Sumpthin's gone away.

Yeah no kidding, Laggy, Like suckin through a smaller straw. So far still no reports, So we're all SNAFUed for the moment. :D

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

They seems down to me, can upload, but not report. Try again later I guess.

Same for me.
Upload good but it's no possible to report (HTTP internal server error).

Bye,
Franz

---

I have the same problems you have. However, I don't get an HTTP internal server error. My error message reads HTTP service unavailable. I've never seen this message before and it keeps recurring since about 17:00 UTC.

---

I have the same problems you have. However, I don't get an HTTP internal server error. My error message reads HTTP service unavailable. I've never seen this message before and it keeps recurring since about 17:00 UTC.

6/10/2007 4:29:00 PM|SETI@home|Scheduler request failed: server returned nothing (no headers, no data)

---

The Cricket graph just nose-dived.

Which one of these is the current: http://fragment1.berkeley.edu/~cricket/? It used to be inr-668 but that obviously changed.

---

This is the link I currently have for the Cricket graph .
If there is a better or different one, maybe someone else can post a link.
Seems like somebody did a reboot about an hour and a half ago, because the forums were offline for a while, but it doesn't seem to have fixed much.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Could this have something to do with it ?

sah_splitter1 kosh Not Running
sah_splitter2 klaatu Not Running
sah_splitter3 penguin Not Running

Regards
XP User

The Server Status page is being updated again, but that really doesn't say much. The splitters are down, but if I can't report or get new WU's that's beside the point. At least 6 out of my 7 crunchers were running with a good sized buffer.
PS- This board is SLOW! It reminds me of downloading files with a TI 99/4A over a 110 baud acoustic modem.

---

Boinc Button Abuser In Training >My Shrubbers<

The Server Status page is being updated again, but that really doesn't say much. The splitters are down, but if I can't report or get new WU's that's beside the point. At least 6 out of my 7 crunchers were running with a good sized buffer.
PS- This board is SLOW! It reminds me of downloading files with a TI 99/4A over a 110 baud acoustic modem.

Ditto here OHM, Except It's only 5 here.

In My case It was an Atari 400 with a 300baud modem while calling a BBS in Hawaii from California, almost.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Well, I was able to upload my finished WU`s without any problems, but since then I get these messages (never had them before)

10.06.2007 23:32:56|SETI@home|[file_xfer] Throughput 91714 bytes/sec
10.06.2007 23:33:05|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:33:05|SETI@home|Requesting 956824 seconds of new work
10.06.2007 23:35:10|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:35:10|SETI@home|Deferring communication for 1 min 0 sec
10.06.2007 23:35:10|SETI@home|Reason: can't parse scheduler reply
10.06.2007 23:36:10|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:36:10|SETI@home|Requesting 958817 seconds of new work
10.06.2007 23:37:15|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:37:15|SETI@home|Deferring communication for 1 min 0 sec
10.06.2007 23:37:15|SETI@home|Reason: can't parse scheduler reply
10.06.2007 23:38:15|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:38:15|SETI@home|Requesting 960147 seconds of new work
10.06.2007 23:39:20|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:39:20|SETI@home|Deferring communication for 1 min 0 sec
10.06.2007 23:39:20|SETI@home|Reason: can't parse scheduler reply
10.06.2007 23:40:21|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:40:21|SETI@home|Requesting 961357 seconds of new work
10.06.2007 23:41:26|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:41:26|SETI@home|Deferring communication for 1 min 0 sec
10.06.2007 23:41:26|SETI@home|Reason: can't parse scheduler reply
10.06.2007 23:42:26|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:42:26|SETI@home|Requesting 962700 seconds of new work
10.06.2007 23:43:31|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:43:31|SETI@home|Deferring communication for 1 min 9 sec
10.06.2007 23:43:31|SETI@home|Reason: can't parse scheduler reply
10.06.2007 23:44:42|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:44:42|SETI@home|Requesting 964411 seconds of new work
10.06.2007 23:45:52|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:45:52|SETI@home|Deferring communication for 6 min 29 sec
10.06.2007 23:45:52|SETI@home|Reason: can't parse scheduler reply
10.06.2007 23:52:23|SETI@home|Sending scheduler request: To fetch work
10.06.2007 23:52:23|SETI@home|Requesting 969294 seconds of new work
10.06.2007 23:53:33|SETI@home|[error] No start tag in scheduler reply
10.06.2007 23:53:33|SETI@home|Deferring communication for 13 min 34 sec
10.06.2007 23:53:33|SETI@home|Reason: can't parse scheduler reply
What ìs the meaning of "no start tag" Regards XP User

Yup, the Berkeley Monster is up and plodding when no one is about again.
Thankfully the ghostbusting squad will be back in around 15 hours.
Even these message boards are slow.

Graeme.
www.boincuk.com

---

Well would you look at that, clicked once, got sick of waiting for it to post so I added to the first message "even these message boards are slow" clicked once more then went to the server status page and when I come back I find a posting in triplicate!

Post one get two free!
(POGTF)

Graeme.

---

uploading OK. Reporting is slow. Downloading new work non-existent. I just changed my cache back to one day from two days, yesterday because I thought everything was stable again.