I just got back on the Seti/Bionic bandwagon and the uploads seem to work but I can't give them my work completed either.
They must be swamped on the incoming band or something.
I get the same error.15/10/2006 7:37:50 AM||Starting BOINC client version 5.4.11 for windows_intelx86
15/10/2006 9:21:55 AM|SETI@home|Temporarily failed upload of 17oc03aa.3123.656.1034670.228_3_0: Error 403
15/10/2006 9:21:55 AM|SETI@home|Backing off 8 minutes and 36 seconds on upload of file 17oc03aa.3123.656.1034670.228_3_0
15/10/2006 9:30:32 AM|SETI@home|Started upload of file 17oc03aa.3123.656.1034670.228_3_0
15/10/2006 9:30:34 AM|SETI@home|Temporarily failed upload of 17oc03aa.3123.656.1034670.228_3_0: Error 403
15/10/2006 9:30:34 AM|SETI@home|Backing off 6 minutes and 8 seconds on upload of file 17oc03aa.3123.656.1034670.228_3_0
15/10/2006 9:34:09 AM|SETI@home|Started upload of file 18ja04aa.672.5073.909672.23_3_0
15/10/2006 9:34:10 AM|SETI@home|Temporarily failed upload of 18ja04aa.672.5073.909672.23_3_0: Error 403
15/10/2006 9:34:10 AM|SETI@home|Backing off 2 hours, 25 minutes and 56 seconds on upload of file 18ja04aa.672.5073.909672.23_3_0
15/10/2006 9:34:16 AM|SETI@home|Started upload of file 17oc03aa.3123.656.1034670.228_3_0
15/10/2006 9:34:17 AM|SETI@home|Temporarily failed upload of 17oc03aa.3123.656.1034670.228_3_0: Error 403
15/10/2006 9:34:17 AM|SETI@home|Backing off 1 hours, 26 minutes and 40 seconds on upload of file 17oc03aa.3123.656.1034670.228_3_0
15/10/2006 9:38:31 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15/10/2006 9:38:31 AM|SETI@home|Reason: Requested by user
15/10/2006 9:38:31 AM|SETI@home|(not requesting new work or reporting completed tasks)
15/10/2006 9:38:36 AM|SETI@home|Scheduler request succeeded
15/10/2006 9:39:21 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15/10/2006 9:39:21 AM|SETI@home|Reason: Requested by user
15/10/2006 9:39:21 AM|SETI@home|(not requesting new work or reporting completed tasks)
15/10/2006 9:39:26 AM|SETI@home|Scheduler request succeeded
15/10/2006 9:57:22 AM|SETI@home|Started upload of file 18ja04aa.672.5073.909672.23_3_0
15/10/2006 9:57:27 AM|SETI@home|Temporarily failed upload of 18ja04aa.672.5073.909672.23_3_0: Error 403
15/10/2006 9:57:27 AM|SETI@home|Backing off 1 hours, 17 minutes and 58 seconds on upload of file 18ja04aa.672.5073.909672.23_3_0

---

Same problem/2waiting/Ontario Canada

---

10/16/2006 9:00:27 AM|SETI@home|Scheduler request failed: Error 400
10/16/2006 9:00:27 AM|SETI@home|Deferring scheduler requests for 45 minutes and 54 seconds
10/16/2006 9:08:16 AM|SETI@home|Started upload of file 20my03aa.16854.32466.217334.3.222_1_0
10/16/2006 9:08:17 AM|SETI@home|Temporarily failed upload of 20my03aa.16854.32466.217334.3.222_1_0: Error 400
10/16/2006 9:08:17 AM|SETI@home|Backing off 1 hours, 42 minutes and 11 seconds on upload of file 20my03aa.16854.32466.217334.3.222_1_0
10/16/2006 9:12:43 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
10/16/2006 9:12:43 AM|SETI@home|Reason: Requested by user


I was getting the 403 Error now I'm getting 400 Error from trying to use proxy. It would seem the server is not accepting any completed tasks. Hope this is fixed soon I have 10 to upload and climbing.

---

From an old tech news:

August 2, 2006 - 17:30 UTC
We had to bring down the project briefly to reboot the upload server. Once in a while it loses random NFS mounts, this time resulting in the inability for the assimilator to insert into the science database, and for results to be uploaded in general.

I guess "once in a while" has come round again.

same problem / Czech republic

15.10.2006 12:38:17|SETI@home|Temporarily failed upload of 22my03aa.7852.26720.340900.3.43_3_0: Error 403
15.10.2006 12:38:17|SETI@home|Backing off 3 hours, 26 minutes and 31 seconds on upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:49|SETI@home|Started upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:51|SETI@home|Temporarily failed upload of 22my03aa.7852.26720.340900.3.43_3_0: Error 403
15.10.2006 14:46:51|SETI@home|Backing off 18 minutes and 4 seconds on upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:53|SETI@home|Started upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:55|SETI@home|Temporarily failed upload of 22my03aa.7852.26720.340900.3.43_3_0: Error 403

On 3 of my machines I have uploaded results from completed WUs OK a few hours ago, and was able to force a "waiting to report" to "acknowledged" all right!.

On one machine I have a WU trying to upload and failing, with ...

15/10/2006 01:11:54|SETI@home|Started upload of file 30oc02aa.8327.18378.673578.3.162_0_0
15/10/2006 01:11:55|SETI@home|Temporarily failed upload of 30oc02aa.8327.18378.673578.3.162_0_0: Error 403
15/10/2006 01:11:55|SETI@home|Backing off 2 hours, 17 minutes and 50 seconds on upload of file 30oc02aa.8327.18378.673578.3.162_0_0
15/10/2006 01:11:57|SETI@home|Started upload of file 30oc02aa.8327.18378.673578.3.162_0_0
15/10/2006 01:11:58|SETI@home|Temporarily failed upload of 30oc02aa.8327.18378.673578.3.162_0_0: Error 403
15/10/2006 01:11:58|SETI@home|Backing off 3 hours, 49 minutes and 34 seconds on upload of file 30oc02aa.8327.18378.673578.3.162_0_0

Anyone else with this problem?

Looking around the Server Status and Cogent Link graphs I can see no reason for a failure to connect.

---

I can not upload from Virginia. I'm glad I can still download WUs.

Chris.

---

same problem / Czech republic

15.10.2006 12:38:17|SETI@home|Temporarily failed upload of 22my03aa.7852.26720.340900.3.43_3_0: Error 403
15.10.2006 12:38:17|SETI@home|Backing off 3 hours, 26 minutes and 31 seconds on upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:49|SETI@home|Started upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:51|SETI@home|Temporarily failed upload of 22my03aa.7852.26720.340900.3.43_3_0: Error 403
15.10.2006 14:46:51|SETI@home|Backing off 18 minutes and 4 seconds on upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:53|SETI@home|Started upload of file 22my03aa.7852.26720.340900.3.43_3_0
15.10.2006 14:46:55|SETI@home|Temporarily failed upload of 22my03aa.7852.26720.340900.3.43_3_0: Error 403

I just suspended my network activity. Lost two WUs to validate errors which hurts with my poor old slow machines. Got about a half dozen completes waiting to send back to Berk. Hope this doesn't last too long. Glad I'm set to a five day cache.

---

PROUD MEMBER OF Team Starfire World BOINC

— By the way, these wu's waiting for upload are occupying RAM are they not? Am I better to suspend S@h alltogether at the moment and would that clear the RAM from s@h-wu's waiting for upload?

WUs that have been completed are NOT stored in RAM, as this would cause them to be lost if you turn off your machine!!!

While WUs are being crunched, they are held in RAM, as well as the original which is kept on your hard drive. By default, the results crunched are svaed to HDD every 60 seconds, so if you stop BOINC, turn off your machine, have a power failure, etc, the work is not lost, and resumes when you restart BOINC.

Similarly, the result is stored on HDD until you upload to S@h.

---

From an old tech news:

August 2, 2006 - 17:30 UTC
We had to bring down the project briefly to reboot the upload server. Once in a while.......

I guess "once in a while" has come round again.

Yes. It seems you've got the reason.
I, too have the 403 error (apparently "forbidden access).
Wouldn't it be nice if SETI had the decency to post the news of a problem like this on Tech Notes?
Seems they have no thought of informing the faithful.
Just an acknowledgement that the problem has arisen and is being looked into would suffice.
Shades of the old SETI Classic apalling lack of information.
It may be that the "fixed version" of the Scheduler (mentioned on 12th Oct) has failed?

October 12, 2006 - 19:00 UTC
A new scheduler was installed the other day and there was a small bug regarding user preferences which has since been found and fixed. The fixed version will be employed shortly.

Keith

sah_assimilator_nonenh kryten Disabled
sah_assimilator1 kryten Running
sah_assimilator2 kryten Running
sah_assimilator3 kryten Running
sah_assimilator4 kryten Running
Is this the problem

---

Old enough to know better(but)still young enough not to care

sah_assimilator_nonenh kryten Disabled
sah_assimilator1 kryten Running
sah_assimilator2 kryten Running
sah_assimilator3 kryten Running
sah_assimilator4 kryten Running
Is this the problem

John that's the NON enhanced assimilator, It's been that way since Non enhanced work left the system sometime in May/June.

tony

sah_assimilator_nonenh kryten Disabled
sah_assimilator1 kryten Running
sah_assimilator2 kryten Running
sah_assimilator3 kryten Running
sah_assimilator4 kryten Running
Is this the problem

John that's the NON enhanced assimilator, It's been that way since Non enhanced work left the system sometime in May/June.

tony

My mistake,but as all the other servers are reported as running I took it for granted this was the problem.So has anybody else got any sugestions?

---

Old enough to know better(but)still young enough not to care

Gee, I only have 3 WU's awaiting upload, getting 403 errors. Now I don't feel so bad. lol

---

Well, 113 WUs trying to upload and rising. I hope somebody at Berkeley can stop in at the shop after church this morning and put things right......
Wouldn't you kinda' think that they would designate 1 person each weekend to be on call in the case of a system crash?

---

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

Well, 113 WUs trying to upload and rising. I hope somebody at Berkeley can stop in at the shop after church this morning and put things right......

That number is not even a full day's output of your Core 2 systems + the rest. I reckon that 1 day's worth of out put would see you queuing juct under 160.

I doubt whether the S@H staffers even know of the upload problem, unless they are crunching (like Matt does). However, they need to check their own systems to become aware.

I expect this will be sorted some time around 1800 UTC tomorrow!

---

It's good to be back amongst friends and colleagues

I'm sure they will get around to fixing the problem eventually...I'm getting the 403 upload error as well, Can you people download new WU's? I've got more than enough at the moment, but I was just wondering if this was limited to uploading...

---

Human Stupidity Is Infinite...

I'm sure they will get around to fixing the problem eventually...I'm getting the 403 upload error as well, Can you people download new WU's? I've got more than enough at the moment, but I was just wondering if this was limited to uploading...

Not as far as the indications seem to point at. However, I am sure that a limit will be hit at some time as no results are being returned.

---

It's good to be back amongst friends and colleagues

Um, I am kinda new to this, but is there any danger of data corruption? I've got six units in various states of uploading (3-5% complete), and I am concerned that when the system comes back on that they won't successfully finish. If that happens I will not be happy.

P.S.: Nice Superpi Msattler! Conroe?

There is very little risk of data corruption.

IMO, the biggest problem is that we expect SETI to be Amazon.com, and the requirements are just not the same.

For Amazon.com, an outage means lost sales.

For SETI, an outage generally means results will be received, validated and assimilated a little later.

It's nothing to worry about.

---

P.S.: Nice Superpi Msattler! Conroe?

You betcha! X6800 on a P5W-DH with OCZ ram at 3-3-3-10 timings.
I actually just ran it again with the tighter ram timings and got 13.422, I'll have to update my sig. Thanx for noticing!

---

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