Oct 18 11:06:46 server systemd[529]: rc-local.service: Failed at step EXEC spawning /etc/rc.local: Exec format error Oct 18 11:06:46 server systemd[1]: rc-local.service: Control process exited, code=exited status=203 Oct 18 11:06:46 server systemd[1]: Failed to start /etc/rc.local Compatibility. Oct 18 11:06:46 server systemd[1]: rc-local.service: Unit entered failed state. Oct 18 11:06:46 server systemd[1]: rc-local.service: Failed with result 'exit-code'.........

When manually running it for some reason it decided to ask for/use the CD as a source whichInever set. Disabling the CD as a source stops this from happening, otherwise apt-get will keep respawning and use 100% CPU.........

After some fsck issues I can't boot my Centos 6.4, this just keeps repeating over and over. init: tty (/dev/tty2) main process (1031) terminated with status 1 init: tty (/dev/tty2) main process ended, respawning Disabling SELinux through Single User mode fixed this.........

This booting error is because the Xen PV guest image uses the Xen kernel, this is not compatible with anything but a host running a Xen kernel. I did a kpartx -av virtual.img and then it created some partitions that showed up in fdisk. I mounted it and did a chroot into it and removed the xen kernel and installed a normal kernel but Xen still shows the same kernel in Grub (only the Xen one). This is strange but it seems like this Xen PV guest has some sort of hidden or........

This server was experiencing loads of up to 80 and maxing out the RAM and kmemsize on a CPanel VPS. There were literally dozens if not hundreds of exim processes. I have no idea why exim has such a design that would allow it to consume this much CPU and RAM. Any normal MTA should not be spawning so many processes, it should be processing them in sequence and if it is going to spawn hundreds of processes in response to a large volume of mail, it's better to have a delayed del........