Most of my errors are IO errors.. Which if everyone recalls, was a fairly major propblem only a few weeks ago.. (Maybe two months or so)... So, with the migration, there might be something going on in the back ground that they havnt told us about causing the IO. Either that or the bandaid solution has failed. Who knows.. Another disk might have died...

---

- cJ

Either that or the bandaid solution has failed. Who knows.. Another disk might have died...

This is what I'm concerned about. I just downloaded two with no problem, can't upload a bit though. yes, this is real familiar.

I just got half of mine to u/l

---

- cJ

My uploads are failing with a -500 IO error which according to the information given out during the last major outage is an internal server error in Berkeley.

So guess the Cricket graphs will show normal usage, and those great long suffering guys at Berkely will fix it tomorrow after they've had some sleep. Don't Worry about it.

If you worry about what is going to happen and worry about what has happened you'll be pushing up the daisy's soon.

Andy

One of my systems finally got it's units to upload, but 2 stuck downloading. It requested more later and they downloaded good. The 2nd system is still waiting to upload. Next week I think I will set BOINC to no network access untill a while after the down time for maintence. No I will probably forget that it is Wendsday, with being retired I louse track of what day it is, all the same now.

---

Pizza@Home Rays Place Rays place Forums

The problem is only with the 'backlogged' transfers -- that is, if when I have a 'new' unit that is ready, it uploads just fine. But any units I have locked in the 'Transfers jail' is not getting out -- be it a download or an upload.

Seems the problem is with some dysfunction at the Berkeley side - perhaps something that happened during their weekly 'offline for backup' cycle today.

I see status page says OK, pinging OK, (see other thread for my tracert issues) I also have WUs waiting for upload, so don't feel alone. It seems to have started after they came back up from the "scheduled" weekly outage for back up purposes.

tony

---

I'm starting to get some UL's .. now .. Yaho !

---

Check the server status page!

BOINC database jocelyn Running
master science database castelli Running
data-driven web pages klaatu Running
upload/download server kryten Running
scheduler galileo Running
feeder galileo Running
sah_splitter1 galileo Running
sah_splitter2 milkyway Running
sah_splitter3 philmor Running
sah_splitter4 kosh Running
sah_splitter5 sagan Running

[As of 13 Oct 2005 4:10:07 UTC]

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

Check the server status page!

And for those needing a further "numbers fix", there's my past 2 week's worth of numbers page. It would appear that something good, bad or ugly... different at least... happened with the outage today.

Right -- seems that for whatever reason at the moment (at least for me) the only ongoing problem (which started today) is in my 'transfers jail' -- though some are getting through from there as well -- just not as reliably. It might clear out by tomorrow though.

And for those needing a further "numbers fix", there's my past 2 week's worth of numbers page. It would appear that something good, bad or ugly... different at least... happened with the outage today.

---

For me at least, it looks like the problem has been fixed, as both my computers have uploaded all their units now.

Andy

Hello dudes and fellow BOINC users!

Some how I'm glad to see that I'm not the only one with this upload issue ;).
All though I'm still not able upload any WU's. I have about 13 WU's in cue now and it's about 11 hours since the backup was done.

I'm I now the only one here that still got this problem!?

<< Greetings from a cold Sweden =) >>

---

DOH!!

Just because I took the time to write here, my computer started to upload the WU's!! *lol*

So.. eh.. thanks? =)

Ciao!

---

Well I'm still getting:

13/10/2005 08:36:16	840	Attempting to communicate with [setiboincdata.ssl.berkeley.edu] timed out
13/10/2005 08:36:16	841	Temporarily failed upload of 01my04aa.20960.29041.953400.43_3_0: timeout
13/10/2005 08:36:16	842	Backing off 4 minutes and 51 seconds on upload of file 01my04aa.20960.29041.953400.43_3_0

On all 4 clients. Something un-cool has occured.

---

Well it's now > 12 hours since the system started to try to come back to life, so i think something more important is broken... I'm very eager to read the excuse they thought up this time ;)
Please not again the usual raid array failure, i want something new :P
Remember: If it's not broken, fix it, til it's broken... :lol:

---

Aloha, Uli

Same Problem here, upload is impossible, download dont work also.

---

Same here my WU has been uploading for five minutes and nothing on my 856 machine whilst my other machine took two minutes to upload. Is it the same problem? I suppose we will have to wait until berkeley boffins are up and about. I think that they are eight hours behind BST or severn behind UTC.

---

[quote]I'm starting to get some UL's .. now .. Yaho !


Hey Byron, glad to see you on deck, we were starting to worry about you.

---

Well.. seems like I was fooled. I thought everything was fine when 1 WU started to upload. But now everything is back to eh "normal" ?

At least I'm still able to download new WU =)

----------------------------------------------------
Try not. Do or do not. There is no try.

Ok. Back from work. So far all of my WU's that were trying to upload HAVE uploaded SUCCESSFULLY :) Whatever the issue was It now seems to be fixed...at least I hope so :)

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3