Apache and MySQL not working well after extending filesystem

Posted by xtrimsky on Server Fault See other posts from Server Fault or by xtrimsky
Published on 2012-06-02T16:30:55Z Indexed on 2012/06/02 16:42 UTC
Read the original article Hit count: 242

Filed under:
|
|

I had 4Gb on my /var (/dev/mapper/vg00-var) filesystem, and I wanted to extend it to 160Gb.

I did it following this tutorial: http://faq.1and1.com/dedicated_servers/root_server/linux_admin_help/7.html

Now I have 160:

Filesystem             Size   Used  Avail Use% Mounted on
/dev/md1               4.0G   424M   3.6G  11% /
/dev/mapper/vg00-usr   4.3G   1.4G   3.0G  32% /usr
/dev/mapper/vg00-var   198G   6.5G   192G   4% /var
/dev/mapper/vg00-home
                       4.3G   4.4M   4.3G   1% /home
none                   1.1G      0   1.1G   0% /tmp

Now I have a problem, in order for Apache to work, each time I reboot, I need to also reboot apache: "apachectl -k restart" which is already terrible. I think this is because /var contains the htdocs

The worst part is, mysql is not starting at all. Mysql has some files also in /var

What have I done wrong ?? :(

Thank you

EDIT: Attaching /var/log/mysqld.log:

120602 11:17:44  InnoDB: Waiting for the background threads to start
120602 11:17:45 InnoDB: 1.1.8 started; log sequence number 8354009
120602 11:17:45 [ERROR] /usr/libexec/mysqld: unknown variable 'set-variable=local-infile=0'
120602 11:17:45 [ERROR] Aborting

120602 11:17:45  InnoDB: Starting shutdown...
120602 11:17:46  InnoDB: Shutdown completed; log sequence number 8354009
120602 11:17:46 [Note] /usr/libexec/mysqld: Shutdown complete

120602 11:17:46 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

© Server Fault or respective owner

Related posts about apache2

Related posts about mysql