Backups backed up and successfully restored to DR server as at 2016-04-29 02:00hrs

NPLB email notification hiccup:
The server is running fine, but the email service has started queueing on the server (all admin notifications to me, so far, no prime notifications yet).
I will be back at the console in about 12 hours to investigate and resolve.

NPLB server is 404.

Wrong. NPLB server is \(2^2\cdot 101\).

[QUOTE=LaurV;440580]Wrong. NPLB server is \(2^2\cdot 101\).[/QUOTE]

:tu: :davar55:

Looks like it is down while I'm out of town. I'll be back late Friday and will look into the issue at that time. Sorry for the problem.

Servers are back up. Sorry for the outage.

It looks like the email queueing may have been a symptom because when you got us back online they all came through to me at once.
I have mail. Lots of mail :P

As often happens, the contents of the log files show me that the server was running fine the whole time. It was just the connection to it that was impaired, so the server was unable to contact the dynamic DNS server to update it's location.
Router manufacturers could add a scheduled reboot feature. That'd be useful.

NPLB server just started getting error responses from the DNS host again in the last 2 hourly dyanmic DNS resfreshes.
Investigating...

it went away again not long after.
Just some random wierdness from the dynamic DNS provider host.

Looks like the noprimeleftbehind.net server is offline/down - I can't connect (either by web, PRPnet or SSH).

Based on my PRPnet clients it looks like it's been out since about midday (server time) on 3/15. Hard to get an exact fix on exactly when it went out since the clients I can readily check were doing multi-hour tests (CRUS).