Our Co-Location Provider, IsoFusion sent us this:

      We are preforming network maintenance on October 8th, Thursday, at 12:00AM PDT and the maintenance window will be till 2:00AM PDT. This may cause outages for 10 to 20 minutes during this time window.

     The command quota -v does not work because rpc.rquotad under Ubuntu 15.04 segfaults right away.  I do not yet know what is causing this but it seems to be fairly unique to us because I’ve Google’d and DuckDuckGo’d and found nada.

     It might be that it isn’t working right with RAID devices, or I’ve got something wrong in the fstab or maybe it doesn’t like the i7-7400k CPU (new CPU only out about a month), who knows.  Initially quota -v also core dumped on the server but upgrading the kernel from 3.19.0 to 4.2.3 resolved this so at least the command works on the server.

     If you believe you are running up against your quota, du -s ~ will at least give you an approximation.  If it doesn’t give you enough e-mail support or create a ticket and I’ll look it up manually and e-mail the results.

     This is not to say that I’ve given up, but it is a difficult problem.  If anyone knows where to obtain source for an older version of rpc.rquotad, please let me know.

     Lost another customer to death, found out today, but he Richard Arnold had passed away in March this year.  I always hate to lose customers but especially this way.

     There will be a brief interruption of all services around 4pm today in order to reboot what is now serving as the main file server. (mail spool will be moved back to another machine after it is configured with RAID10 file systems and better cooling).

     This is necessary in order to install a kernel that fixes some interrupt latency issues that is causing a higher load than should exist given that CPU and I/O utilization are very low.

     Normally I would be doing this late at night but because the last two reboots have had complications that required a trip to the co-location facility, I want to be on-site when I do this and I need to make a trip to Fry’s to pick up a cabinet and cooler for the machine being reconfigured.

    The client mail server, mail.eskimo.com, has been moved to new hardware and is back online and available for use.

     Shellx is moved to the new hardware, up and available for use.

     The shell server shellx, UUCP machine, and mail server are all going down to move to new hardware.  Shellx first, then UUCP, then mail.  An downtime of about 30 minutes is expected for each.

     The web and ftp servers are now on the new machine.  I’ve mostly got it working.  The one thing that is still broken is the ability to use quota -v.  For some reason it core dumps on the host, and on the guests it says can’t connect with the quota daemon.  It may be a firewall issue.

     I’ve got virtual machines working with networking fully functional and was able to move a guest virtual machine from a CentOS 6.7 host machine to a Ubuntu 15.04 host machine.

     What I am going to do now is move the rest of virtual guess off of Iglulik and move the guts to a bigger case and replace the Intel stock useless cooler with an evo212 like I used on the new box and that will allow it to perform better.  Presently it gets too hot and throttles the CPU slowing things down.

     Then I will reload Iglulik with Ubuntu 15.04 like I have on the new machine.  I’ll add some disks and configure the important stuff raid10 as with the new box.  When it’s done, will do the same with virtual.  Then we’ll have a good modern OS on all the host machines and adequate cooling for them to run full tilt.

    At present everything is in place to provide Private Virtual Servers.  If you want one, talk to me.  I’ll have details on the website in a few days.

     Trying to create a bridge on the new server for virtual machines, when I attempted to put it into service it failed because I had neglected to tie the Ethernet on the local machine to it, isolating it from the network.

     Another drive to the co-lo facility was necessary.  Sorry for the interruption.

     Sorry for the downtime tonight.  To put it mildly things did not go as planned.  Needed to reboot the new server to remount some mount points and instead of booting it hung on a lightdm shutdown.  Before it was in actual duty I’d done this a few hundred times without incident.

     Also for some reason virtual machines aren’t working with static IP addresses on the new box.  But things should be up and running.  Sorry for this downtime.  It’s in the interest of making things faster, more redundant (all customer data is now on RAID except for MySQL and it will be once I get this virtual host routing issue figured out.