If you get this error, it is often because you have configured Apache with modules that weren't actually installed. Eg. you try to load the PHPmodule but didn't actually install the apache2 php module, so the server can't start. In general, this error can often be caused by issues with problematic modules and/or Apache being configured for modules that have not actually be installed (eg. libapache2-mod-php) is missing. The above results in this less than obv........

yum -y install mariadb-server systemctl start mariadb mysql_secure_installation Now we need to secure our install and set the MariaDB root password: The lines you need to act on are marked in bold shown with the answer you need. mysql_secure_installation NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB SER........

growisofs -Z /dev/sr0 critical.tar.gz.gpg Executing 'genisoimage critical.tar.gz.gpg | builtin_dd of=/dev/sr0 obs=32k seek=0' I: -input-charset not specified, using utf-8 (detected in locale settings) File critical.tar.gz.gpg is larger than 4GiB-1. -allow-limited-size was not specified. There is no way do represent this file size. Aborting. :-( write failed: Input/output error #remember to us........

sudo apt-get install zoneminder [sudo] password for one: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libuser-perl python-evince kdebase-apps kwrite unixodbc libgnomeprint2.2-data python-soappy vgabios python-metacity hddtemp python-mediaprof........

I closed program by program untilI found the culprit, it's baffling how the cause was Thunderbird but then again it does use a lot of memory and I have thousands of messages between dozens of mailboxes. But still I don't think this should happen and Xorg shouldn't allow this either. So for those who have mysteriously high CPUusage from Xorg start closing program by program until you find the culprit. The interesting thing is that after reloading it, the Xor........

ifup eth0 SIOCSIFFLAGS: Cannot allocate memory Failed to bring up eth0 This is on a Centos 5.5 machine with OpenVZ kernel 2.6.18-238.12.1.el5.028stab091.1PAE, I updated 3 systems with the same hardware to the same kernel and for some reason the network didn't come back. This only happened once the first time I booted into the new kernel and hasn't happened again but this is a serious issue for those running systems from remote locations such as a datacente........