Does someoneelse get the 403 error now?

Getting the same here on all 4 machines. I assume it is because Seti has changed upload port and/or IP address and my router needs to know it but I dont know for sure. I was port monitoring and when I told it to upload results, no port opened. It just said it was attempting and immediately died with this error. I updated from Boinc 5.48 to 5.49. 5.48 wasnt doing this.

Does someoneelse get the 403 error now?

Getting the same here on all 4 machines. I assume it is because Seti has changed upload port and/or IP address and my router needs to know it but I dont know for sure. I was port monitoring and when I told it to upload results, no port opened. It just said it was attempting and immediately died with this error. I updated from Boinc 5.48 to 5.49. 5.48 wasnt doing this.

gregh, the correct version number format for the BOINC cc is 5.4.9

---

_\|/_
U r s

Does someoneelse get the 403 error now?

Getting the same here on all 4 machines. I assume it is because Seti has changed upload port and/or IP address and my router needs to know it but I dont know for sure. I was port monitoring and when I told it to upload results, no port opened. It just said it was attempting and immediately died with this error. I updated from Boinc 5.48 to 5.49. 5.48 wasnt doing this.

Nope the assimilators which deal with uploads are just off-line so things will return to normal when they are restarted. For the moment downloads are working fine so no one will run out work. no panic

---

Does someoneelse get the 403 error now?

Getting the same here on all 4 machines. I assume it is because Seti has changed upload port and/or IP address and my router needs to know it but I dont know for sure. I was port monitoring and when I told it to upload results, no port opened. It just said it was attempting and immediately died with this error. I updated from Boinc 5.48 to 5.49. 5.48 wasnt doing this.

Nope the assimilators which deal with uploads are just off-line so things will return to normal when they are restarted. For the moment downloads are working fine so no one will run out work. no panic

---

Cant upload error 403 for all my wus from last night
Validation error for the WUs
;-) no happy crunching

validate error

They will fix it for sure after the outage.
Better no uploads til then.

Mike

---

With each crime and every kindness we birth our future.

They will fix it for sure after the outage.
Better no uploads til then.

Mike

I support Mike's comments.

We cannot expect the SSL staff at Berkeley in for at least another 3-4 hours from this message (current UK time 2.00 pm BST - UTC+1 hour). Then there will be the usual database compression and back up outrage for another 3-4 hours.

I do not expect the upload problem to be fully sorted out until the normal Tuesday outrage is over. Say in the 10 hours.

The 403 errors relate to Kryten, which is both the assimilators (4 off) and the upload/download server. Other posts in these threads comment on the assimilator server status.

I now see both 4.18 and 5.12 completed WUs are affected,, as I have a number (33) waiting to go!

---

It's good to be back amongst friends and colleagues

Nope the assimilators which deal with uploads are just off-line so things will return to normal when they are restarted. For the moment downloads are working fine so no one will run out work. no panic

So can I assume that all will be well and we'll get credit for the Vaidate error work once "kryten" is fully back online? I currently have over 50 hours worth of work showing Validate Error :(

---

D.

So can I assume that all will be well and we'll get credit for the Vaidate error work once "kryten" is fully back online? I currently have over 50 hours worth of work showing Validate Error :(

a similar problem with validation occured over at Einstein last friday.
they had to reissue the work with the validation-errors and run a script to grant credit once the reissued results were returned and validated.

as well as getting a 403 when trying to upload to SETI, i'm also getting a 403 when trying to download from SETI beta

although i can contact both schedulers with no problems, so i think this must be a data server issue (both projects use the same data server as far as i know)

---

Want to search the BOINC Wiki, BOINCstats, or various BOINC forums from within firefox? Try the BOINC related Firefox Search Engines

Interesting occurence during this 403 outage. I had 2 5.12 enhanced WUs report and both errored out as invalid (had been uploaded prior to the server issue). This is the first time I have had this machine not validate (including 5.12 WUs).

The 2 WUs can be found here and here.

A strange coincidence that may be related and if it is may affect others (30,000 seconds of crunch time wasted in my case).

Anyone have any ideas if these 2 events are related?

---

!!Stupidity should be PAINFUL!!

a similar problem with validation occured over at Einstein last friday.
they had to reissue the work with the validation-errors and run a script to grant credit once the reissued results were returned and validated.

So worst case scenerio here is that I've lost 50+ hours of processing time? Now that would be discouraging... :(

---

D.

Well, on top of this error, I just looked at 1 of my computers. I have 3 4.18 WU's, and 1 enhanced, but looking on my account for this computer it says I have 7 wu's for this computer. I'm thinkin some of these are those mysterious "ghost" WU's. Dunno if anyone else is having the same issue, just though I would point it out.

Jeremy

---

a similar problem with validation occured over at Einstein last friday.
they had to reissue the work with the validation-errors and run a script to grant credit once the reissued results were returned and validated.

So worst case scenerio here is that I've lost 50+ hours of processing time? Now that would be discouraging... :(

Over at Einstein they kept the invalidated results and issued new results to other machines and then when the newly issued results were returned and validated they ran a script to award the same credit to the invalidated results.
One can only hope the SETI-crew does the same thing in this case.

I see that the assimilators are working again, but I'm still getting error 403 -- I have 10 WUs waiting to upload. Perhaps in an hour or so the problem will resolve.

Few minutes later: Now I'm getting the following, which I think is progress:

5/16/2006 9:37:43 AM|SETI@home|Temporarily failed upload of 30mr99aa.29392.20640.672144.3.230_0_0: system I/O

---

as well as getting a 403 when trying to upload to SETI, i'm also getting a 403 when trying to download from SETI beta

although i can contact both schedulers with no problems, so i think this must be a data server issue (both projects use the same data server as far as i know)

Hi Lee,

I'm also getting hung units on Seti Main & Beta - and the status blocks are all on green. Must be in the connections somewhere . . .

Regards,
Bill_Mole

---

What time (UTC) does the weekly scheduled outage occur?

---

What time (UTC) does the weekly scheduled outage occur?

1700 UTC -- but it looks like it has already started.

---

I don't know but I have had upload problems since last night,
so what ever is up now it's probably not related to the weekly outage...

All services except splitters are green and the your account, message boards, etc. are all working. This is not the weekly shutdown as these features would be unavailable.

Not getting 403 errors any more but getting:

5/16/2006 1:42:47 PM|SETI@home|Temporarily failed upload of 25fe99aa.11655.3330.467332.3.183_3_0: system I/O
5/16/2006 1:48:23 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]

Hope they get it fixed soon, cache is starting to get low as I have 5 WUs waiting for upload and haven't receved any new downloads.

Would be nice if there were some information on the front page or under technical news, but experience tells me that won't happen until after whatever is going on is fixed.

---

!!Stupidity should be PAINFUL!!

Not getting 403 errors any more but getting:

5/16/2006 1:42:47 PM|SETI@home|Temporarily failed upload of 25fe99aa.11655.3330.467332.3.183_3_0: system I/O

Hope they get it fixed soon, cache is starting to get low as I have 5 WUs waiting for upload and haven't receved any new downloads.

If you are also running another project that will by plunty to get you past todays downtime. I have 7 ready to go in, and 6 waiting to be worked but with it getting 1/3rd of the time that will be plunty to last so not worried. Should it run out CPDN and Rosetta will enjoy the extra time.