Eskimo crashed, even though I’ve moved it to different hardware (I am still trying to repair the old), so I will head down to the co-lo in a bit to reboot.
Scientific Linux is slow since moving to new hardware. It’s not load or speed of the new hardware that is the issue, Centos6 is served off of the same hardware and does not have this problem.
Both are derived from the same Redhat 6.8 code, but I’m getting some weird errors on Scientific that I am not getting on Centos6. I’m going to try recreating the virtual machine in a bit and if that does not work perhaps reload it from scratch. I did have to do this with Centos6, (shellx became so corrupted it was unmaintainable). The RPM system that these Redhat derived operating systems use tends to be easily corrupted and difficult to fix beyond a certain point.
But this problem seems to relate to the virtual machine as it worked fine on the old host.
I’ve moved all the services off of failed hardware but because some machines still have file systems mounted off of there and will not let me umount, not even with the force option, I’m going to have to reboot a bunch of stuff to get that corrected so there will unfortunately have to be further interruptions although they should be relatively brief.
I am still in the process of shuffling virtual hosts around to get them all moved off of unstable hardware. Things will lag a bit while this is in progress as copying files of several hundred gigabytes across the net comes close to saturating the ethernet links.
Mail is now available on centos6.
Mail is now available via webmail, smtp/pop3/imap. I am still working on fixing mount points for shell servers. Incoming will be backed up and take a little while to catch up.
The physical machine is up and I have copied the mail spool to a new machine. Now I am moving the virtual machines off of old hardware and changing mount points to reflect the mail spools new location.
The physical host upon which the mail spool sits is down. It is also the NIS slave that many of the machines slave off of so they won’t authenticate.
I have to wait for a ride to get to where my car is and then from there make my way down to the co-location facility. Because it will be rush hour by the time I get to my car it is going to take a while to get to the co-location facility.
Once I get the mail server back up I am going to begin copying the spool from it to another physical machine and then move the virtual hosts off that box. The fact that it has crashed twice in a weeks time suggests there is some marginal hardware issue with the machine.
Since I had planned to upgrade it anyway I am going to move everything off the existing machine and then replace the motherboard, CPU, and memory.
I hope to have the old hardware back up and operational by around 9AM. It just depends upon how bad traffic is.
There is something wrong with a DMA controller on the SS-10 chassis, I have two and they’re both cooked. Going to bring the old server up on an LX, this is seriously under powered. The SS-10 had two 120 Mhz CPUs, this will have one 40 Mhz, The old machine had 512 MB of RAM, this will have 96 MB. So it’s going to be slow as snails until I can locate another SS-10 chassis or find a way to dump the ROMS to a file so I can get emulation working.
The old shell server is seriously broken. It will not boot. Gets data exception errors before you can even finish typing the boot command. Brought it back home to try to determine what. I’m thinking a bad DIMM or CPU is most likely. I have no spares of either so if it is one of the two it is either going to return a single CPU box or with less memory.
If anyone has any SS-10 hardware they want to get rid of or M-Bus CPUs or 64MB DIMMS these things used, I’d be happy to take it off your hand.
This machine is the NIS master so I can not change passwords or enable or disable accounts until I get it operational.
The mail server is up. It was locked up hard, not even the Linux magic sys request key had any effect. Power cycling it brought it back up. Nothing in the logs useful to provide any post mortem information.
This is the only Intel machine still running an I7-2600 rather than an i7-6700k. I am planning on upgrading it soon. The i7-2600 only supports 32gb of RAM where the i7-6700k supports 64gb. You can not give Linux too much RAM, it uses any excess for buffer and that improves performance. There are some newer Intel CPUs available and I have not decided which I am going to go with yet.
The old eskimo.com shell server is not responding. I will need to make another trip down to the co-lo facility to fix that. It is responding to pings but nothing else. This is a wedged state the SunOS kernel occasionally gets into.