All the planned reboots have been completed and NIS/NFS connectivity verified, but Centos7, Scientific7, and MxLinux were all a little slow out the gate with kernel updates so I have to reboot those today.

     Sometime after tonight I’ll be rebooting the majority of servers to install kernel upgrades that address some newly discovered security concerns in Intel processors.  Not all services will be down at once except for a brief period when we reboot the server with the /home user partition.  That should take about fifteen minutes.  This will happen sometime after midnight, probably closer to 2AM.

     Reboots are complete, no further interruptions anticipated tonight.

     We will be rebooting most of our servers (all the Intel based machines) to load a new kernel to address recently discovered security vulnerabilities.

     OpenSuse.eskimo.com is back online but is back on version 15.0 owing to the inability for x2goserver to run on 15.1 because x2goagent is missing.

     Most NextClouds are back online.  Unrecoverable for the time being are OnlyOffice and ZimbraDrive.

     Presently a large number of NextCloud applications are unavailable.

     This is because in a recent update something went wrong breaking one or more of the apps.  With all of the apps enabled it just loads a white page, no errors or clues as to what is wrong even if I turn on php display_errors.

     So to troubleshoot I’ve disabled all apps, which has allowed the page to load and am slowly enabling them to determine which is broken.  This will take a while, please be patient.

     OpenSuse.eskimo.com is going to be down longer than I thought, days, maybe weeks.

     15.1 is installed but I can’t get into any of the graphical tools I need to complete the configuration because x2goserver is broken on it, no x2goagent necessary for x2goserver.

     No idea yet how I’m going to work around this one, maybe vnc or rdp.  At any rate it’s not going to be easy or fast.

     Opensuse.eskimo.com will be unavailable for several hours during upgrade from Leap 15.0 to leap 15.1.  Unfortunately, an in-place upgrade failed requiring a fresh install.  This has never been a simple or straight forward process with Suse so will take a few hours.