Gary can you upload?

Answer is, of 5 boxes I have checked only 1 of them (a Raspberry Pi) has a W/U stuck uploading, but it may be the 4 haven't had a competed W/U since the project went down so they haven't tried to upload.

Also https://albert.phys.uwm.edu is down.

I run the Binary Radio Pulsar Search application. Tasks were downloading, uploading, and reporting OK yesterday while the website was down. But uploads failed around the time that Jim1348 reported that his uploads were stuck, and they haven't moved since.

My CPU uploads are OK; five have gone in the last 10 hours. But GPU uploads are still stuck.
Maybe they go to a different place?

... uploads failed around the time that Jim1348 reported that his uploads were stuck, and they haven't moved since.

Uploads had started failing somewhat earlier. On one of my machines an upload succeeded at 7:42PM UTC (Feb 21st), whilst the next one at 7:59PM, and all subsequent, have been fails. The problem started at least a half hour before Jim's report.

Interestingly, on that same machine, there were a couple of uploaded tasks that were successfully reported at 8:41PM UTC, nearly an hour after the uploads started failing. Not too long after that however, even reporting must have failed since I've noticed another machine with 3 uploaded tasks that hasn't been able to report them.

All my machines are out of work with zillions of tasks stuck in upload and with multi-hour back-offs ticking down. It's around 8:30PM here and I've been hoping the problem gets fixed so that I can run a script to cancel the back-offs and then head off home. The script will also replenish data files from my cache to stop unnecessary downloads for resend tasks that will inevitably turn up once each host is able to start getting fresh work. Hopefully this might get sorted soonish :-(.

---

Cheers,
Gary.

My BRPS tasks are also GPU, and the uploads are sent in the first instance to einstein4.aei.uni-hannover.de

But the ultimate failure, as it has been several times in recent weeks, is HTTP/1.1 504 Gateway Time-out: that's an onwards transmission to another server, with might be either in Hannover or in Milwaukee, Wisconsin.

If it's any consolation, my work fetch blunder
of Tuesday is turning into a much happier
event than it felt at the time. Yes :)

I don't usually have more than 9 Einstein tasks
in progress, but as of 7 this morning, I still had
84 yet to start.

One of the h1 cpu tasks did somehow upload
and report itself midst the carnage of others
that didn't though. I'm not sure what time
that was, although my head is saying it was
around 11pm.

The website is now up, but GPU uploads are not working yet.
I see no explanation on the forums, and will leave it to a knowledgeable person to query them.

Yep. Server status says scheduler daemon is the only one currently running. "The database server is not accessible".

Sawn Kwang has posted in the Technical News area.

It appears they had two separate problems: a power outage and a cooling failure.

On 2019-02-20, at about 1930 UTC there was a power outage at UWM. The E@H Web site front-end went down when the power shut off, but power has been restored.

Update: After power was restored to UWM, the data-center which houses the E@H infrastructure had a cooling failure. The end-result is that we moved servers to a new data-center, ...

Then, there's a second post about networking:

Re the Server Status page: It looks like the server status page is not working; it says everything is down. This is probably due to the networking at UWM is not fully operational yet after the power outage and data-center migration.

I think that's our problem with uploads too. Either the network still hasn't been properly configured for the new IP addresses and routing, or we're still waiting for new DNS settings to propagate. We can't do anything about either.

After a manual retry, all of my GPU work units have uploaded and are reported.
Case closed.

Asteroids is down...

cpdn.org went down a while ago. climateprediction.net front page and static pages are there but no response from servers or forums. Perhaps the wind has brought something down?

cpdn.org went down a while ago.

I have not been able to access my statistics for a day or two. Now I don't even get the front page.
EDIT: Now I get the forums, and now my statistics too. I hope it lasts.

I have not been able to access my statistics for a day or two. Now I don't even get the front page.

The forums are back up and scheduler request just completed. Stats have also just updated.

I think someone has changed the weekly weekend running of the stats batch file for a random number generator.

Looks like Collatz is down. I was having trouble downloading and uploading tasks for the last few hours prior to the shutdown.

---

WCG - Planned Maintenance on Wednesday, May 1, 2019

30 Apr 2019
https://www.worldcommunitygrid.org/about_us/viewNewsArticle.do?articleId=594

Summary
We are updating the operating system on our servers on Wednesday, May 1, beginning at 19:00 UTC.

We will be applying an important operating system update to our servers on Wednesday, May 1, beginning at 19:00 UTC. We anticipate that the work will take approximately two hours.

During some of this time, volunteers will not be able to upload or download new work, and the website will not be accessible.

Volunteers will not need to take any particular action, as your devices will automatically retry their connections after the maintenance work is completed.

---

Collatz now appears to be functioning properly.

---

Collatz Conjecture - Down
Even their website throws errors for me. No communications at all.
Work Units piling up.

Collatz Conjecture Outage: further information

URL: boinc.thesonntags.com/collatz
The URL resolves to 67.167.89.131
This in turn resolves back to "c-67-167-89-131.hsd1.il.comcast.net".

A traceroute suggests the server is down or unreachable:
traceroute to 67.167.89.131 (67.167.89.131), 30 hops max, 40 byte packets using UDP

1 192.168.0.1 (192.168.0.1) 0.769 ms 0.552 ms 0.464 ms
2 * * * LOCAL DETAILS HIDDEN
3 * * * LOCAL DETAILS HIDDEN
4 * * * LOCAL DETAILS HIDDEN
5 * * * LOCAL DETAILS HIDDEN
6 68.86.86.225 (68.86.86.225) 3.131 ms 5.244 ms 4.176 ms
7 68.86.84.206 (68.86.84.206) 32.530 ms 31.859 ms *
8 * * *
9 68.86.85.169 (68.86.85.169) 51.131 ms * *
10 * * *
11 * * *
12 * * *
13 68.87.204.74 (68.87.204.74)(H!) 52.094 ms * *

Note: "H!" = host, network or protocol unreachable
Did someone forget to pay Comcast?

Quite possible that ping is restricted and the root problem is simply a certificate expiring or something annoying like that.