CAcert System Admins discussion list

[Ian G <iang AT cacert.org>]

On 11/01/2010 20:27, Bernhard Fröhlich wrote:

> > For all test1 sysadms: it seems that both Apache and Mysql do not
> > start up properly on reboot. Maybe as a result of chroot and run level
> > changes made in the past? Perhaps we need another go at this, some
> > reboot testing?
...
> Running out of space seems to be not the only problem of test1.cacert.at.
> It was already mentioned that apache did not start automatically, though
> an entry "S91apache2 -> ../init.d/apache2" is present in rc2.d.
>
> The bigger problem was that the php scripts could not contact the mysql
> database. Jan's (probably correct) opinion was that the chrooted apache
> process coult not access the mysql socket at
> /var/run/mysqld/mysqld.sock. So with some trial and error I replaced all
> references to /var/run/mysqld with /chroot/var/run/mysqld in
> /etc/mysqld/my.cnf and /etc/mysqld/debian.cnf.
> Then the mysql user did not have write access to /chroot/var/run/mysqld
> which probably prevented the creation of the socket. Therfore I chowned
> /chroot/var/run/mysqld to mysql.
>
> After some restarting of mysqld the connection now seems to work again.
> I've no idea if my changes are how it should have been done, so probably
> someone more acquainted with debian and mysql configuration thould have
> a look at it. And I wonder why the system did run in the past at all...
>
> Hope this helps


Super...  Time for a reboot?  See if it comes up?

iang

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature