So I have absolutely no idea what's wrong, only that uploads doesn't work. That means the server status page isn't showing correct status (again), which I find quite annoying (can't help it...). Yes yes, there's the cricket page, but that's not the point.

So I have absolutely no idea what's wrong, only that uploads doesn't work. That means the server status page isn't showing correct status (again), which I find quite annoying (can't help it...). Yes yes, there's the cricket page, but that's not the point.

I'm getting "connection refused" as the http_debug report. That suggests that both the network and the server are alive, but that something inside the server is on strike. I'm not sure how closely the server status page can monitor things like that...

I blame the cleaning crew! I bet they tripped over a cable or unplugged the switch to the campus internet link.

---

PROUD MEMBER OF Team Starfire World BOINC

Uploads are now working.


Kevin

---

Kevin

Uploads are now working.


Kevin

I'll confirm that. I just got a few passed down the pipe.

Uploads are now working.


Kevin

I'll confirm that. I just got a few passed down the pipe.

They were flying up there, but have now slowed down, looks like the normal logjam.


Kevin

---

Kevin

Yep, that's the normal logjam alright! Okay, everyone set no network traffic. I'll let you know when mine have finished so you can resume! :-)

---

PROUD MEMBER OF Team Starfire World BOINC

Aah yes that's better now.

Okay, mine have all gone through and I've got new work. You can open yours back up now! :-) Just in time too, I was crunching my last GPU task.

---

PROUD MEMBER OF Team Starfire World BOINC

I've still got a few stubborn tasks that refuse to upload.

---

Try stopping and restarting the BOINC manager if you haven't already done so.

---

I hammered the retry button for my three uploads. Two went through on one try, but the third one took four attempts. The ACK got lost in transit and timed out due to congestion. I've done my part. :p

---

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

Oh dear,

Just got home from work, uploads have finished, as I expected.

Just found a download queue over 1000 units long, Oh well that will keep me going for a couple of days.

---

Kevin

All splitters not online, soon there will be no new work...

if you believe the status page all is WELL

---

if you believe the status page all is WELL

Well mostly green now but when I posted splitters had been offline for some time, guess maybe work will come again shortly...

Missed the point
Status page LIES

---

Status page reflects the status at a moment in time. It is mechanistic - it can't "lie".

F.

---

Status page reflects the status at a moment in time. It is mechanistic - it can't "lie".

F.

However, not all of the information on the status page is from the same moment in time. Last I heard, it takes about 10 minutes for the script that generates all of that information to run through, and that's the update interval for the status page. So the status of one server compared to another can be minutes apart.

That and the script that checks the status also kicks 'not running' (red) processes and tells them to start again. If they are instant-failing for a particular reason, it can be difficult to actually catch that since the script does something similar to "is it running? if yes, move on to the next process. If no, kick. Did the kick make it run again? if yes, it is now running (green) and move on. If no, it is 'not running' (red) and move on."

So if it fails to start running again, it will be red, but if it successfully completes the kick process to fail even a second after finishing the command, it will show green on the status page, even though it should be red.

---

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

Csn't download-almost out of work.....and a switching to backup work

---