Just took the server down for a few minutes to do some upgrades and lose my 377 day uptime.

Now has more RAM, more disk, newer kernel, and newer other stuff that I needed to be new.

More upgrades to come, but most should be down-time free, hopefully.

Fred.

All freeems and fred related sites will be down for up to 2 hours from this date/time: 2015-03-05 11:00:00 AM UTC

Just FYI.

Fred.

I guess all is well in the world, once again.

Reused wording from last time:

All FreeEMS and Fred related sites will be down for up to 2 hours from this date/time: 2015-10-21 9:00:00 AM UTC

That's 9pm on the same day for Kiwis, the rest of you can do the conversion yourself.

Just FYI.

Fred.

Ditto, down for a while following Saturday, July 23, 2016 9:00 AM EDT / Saturday, July 23, 2016 1:00 PM UTC

Hopefully no major drama!

There was a brief downtime earlier this evening when I was purging some very old packages from the server. One of them was an old version of mysql that hasn't run for years. When it was removed, the system stopped mysql, but it stopped the current version as the old one wasn't running. I restarted it and all was well, but there was around 30 seconds downtime :-p

Apologies for the brief downtime in the last hour or so. Machine was migrated to a new host and when it came back up, mysqld was not running, so I had to sort that out. Was only down for a few minutes anyway. Previous uptime 434 days.

10.5 hours from the time of this post the server will be down for up to 2 hours. Just FYI. I'll try to keep an eye on it, but feel free to email me if it doesn't come up cleanly and I need to take action. Cheers.



Forgot to apologise for the brief downtime, I rebooted it a few days ago for Meltdown/Spectre reasons.

(20:06:00) diyefi-bot left the room (quit: Remote host closed the connection).
(20:16:27) diyefi-bot entered the room.

10 minutes down, I don't know about you, but I didn't notice. All seems well.

There was an unexplained reboot a few hours ago which I contacted support about demanding to know why. Logs showed it coming from the hypervisor, by the looks. Will see what they say. Just an FYI in case you hit it in the minutes/seconds it was not online.