To load new kernels that correct some issues with the previous kernel, we will be rebooting all our host machines and most of the guest machines starting at 3AM approximately.
The expected downtime is about five minutes per machine, most things should be complete in 15 minutes, however, occasional NFS problems arise after a reboot and it will take several hours to check all machines for these but most services should be back up by 3:15AM.
Just found out today that one of our customers, Wayne Moddison, passed away in November of last year.
I did not talk to him frequently but he was one of the most pleasant people you could ever want to know and I’m very saddened to hear of his passing.
Taking centos6.eskimo.com down for about 45 minutes to image the virtual machine.
CentOS6 is up and operational on i7-6700k hardware. It is no longer vulnerable to spectre or meltdown exploits and it was the last machine that was vulnerable so all of our systems are now protected from these exploits.
I will be taking CentOS6 down for about 45 minutes tonight, around 1:30AM, to image the machine on the new hardware.
The move of Centos6 is going to take longer than I originally anticipated due both to the size of the machine and the fact that I did not have enough space on the host I had originally intended to move it to so needed to start over moving it to a different machine.
Based upon the rate the copy is going and the amount of data remaining to me moved I estimate another 25 minutes or so. Centos6 should be available again by 16:30 Pacific time.
All machines here have spectre and meltdown exploits mitigated except for CentOS6. Redhat has kicked out a new kernel that addresses the exploit on i7-6700k hardware but does not address it on i7-6850k hardware which is officially not supported by Redhat 6.
Consequently I am in the process of moving this host to an i7-6700k based server. This will take about 1/2 hour during which CentOS6 will be inaccessible. Please use a different shell server during this time. All x2go supported windowing environments are supported on MxLinux and Ubuntu.
The client pop3 and imap4 mail server mail.eskimo.com is now restored from backups, the updates successfully re-applied, and now this machine is no longer vulnerable to either spectre or meltdown exploits.
Our client mail and smtp server is presently down owing to a failed kernel upgrade that mangled the boot block. I am restoring the server from a backup. It should be operational again in about ten minutes.
Incoming mail will still arrive as incoming mail is processed by different servers and you can access it via any shell mail such as pine, mailx, etc but you will not be able to send until this is restored.
Rebooting of all servers completed.
NextCloud update completed. As far as I know everything is operational again.