We are going to be rebooting our physical host machines tonight to install a new kernel that addresses a copy-on-write exploit in the existing kernels. The exploit can not be taken advantage of currently because nobody has access to the physical machines and we do not use KSM which consolidates memory pages because we have enough memory that it is not necessary. At some point in the future however it may be so I want to address this issue and get it taken care of.
Various services will be out of service for approximately 1/2 hour, not all at the same time. If all goes well (sometimes it does not) we should be finished around 1:30AM.
I have installed Komodo Edit 10, a really nice editor for HTML, CSS, PHP, and a variety of computer language source files on Ubuntu, Debian, and Mint.
This is a really nice way to edit your website online here. It is a graphical application so you should use x2go to access the machines in question.
Under the Mate Desktop, Komodo Edit 10 can be found under Applications → Programming → Komodo Edit.
The Ubuntu upgrade from 16.04.1 LTS to 16.10 has been completed. The machine is now ubuntu 16.10.
The existing Ubuntu configuration has been imaged.
I have started the upgrade process to upgrade from 16.04.1 LTS to 16.10. I really don’t like non LTS releases BUT there are so many systemd script related bugs in 16.04.1 that they do not appear interested in fixing that release that I feel if 16.10 can work it’s worth a try. If anything goes terribly wrong I have the image of the existing 16.04.1 LTS so we can always revert if necessary.
I am taking ubuntu.eskimo.com to image the machine prior to initiating an upgrade from Ubuntu 16.04.1 LTS to Ubuntu 16.10. I’ve had 16.10 running on a workstation long enough to feel comfortable upgrading. The only issue I have had with the workstation was an antique nvidia card.
I ended up not getting to doing the web server backup until much later than I had intended. I ran into some problems with the installation of PHP 7.0 that didn’t cause operational problems but did slow down the server somewhat as it attempted to load library extensions that were already compiled in. This was the result of the machine having been upgraded from a previous version that did not have them compiled in but the upgrade did not automatically remove them from the configuration file.
So server is now at the most recent version of everything in the long term support release (I am not upgrading to 16.10 at this time both because it does not seem to offer any significant operational enhancements, and because I have experimented with it on a non-critical machine and found it to be buggy still).
I will be taking the system down for about 20-30 minutes tonight in order to image the machine as I have made a number of significant updates that I wish to backup in case something goes wrong.
I was able to recover all of the mail spool from the failed server image and restore it to the new server image that is fixed and all mail is processing normally.
One of our mail servers somehow corrupted it’s root file system in such a manner that it thinks it is out of free space even though it’s at 61%. The fsck program does not fix whatever is wrong so I am restoring from a virtual machine image backup.
There is quite a lot of mail stuck in spool which I hope to copy from the broken image to the backup image.
If all goes smoothly no mail will be lost and only that stuck in spool will be delayed. If that spool is not salvageable than it is possible for some incoming mail to be lost but I do not expect that to be the case.
The NetBeans 8.2 Integrated Development Environment has been installed on all shell servers except the old “eskimo.com” SunOS machine.
Most will have it as a graphical link on the Gnome or Mate desktop but it can also be found under Applications -> Programming on these machines.