update fails: mysqld.sock assumed to be in hardcoded location

Discussion in 'Installation/Configuration' started by fatbear, May 7, 2016.

  1. fatbear

    fatbear Member HowtoForge Supporter

    I recently did an ispconfig_update.sh and ran into problems:
    Unable to connect to mysql server No such file or directory
    MySQL root password [xxxxxxx]:
    The problem it turns out is that my socket file path is (my.cnf):
    socket = /var/lib/mysql/mysql.sock
    The updater seems to be hard coded to look for it in:
    I was able to complete the update by doing:
    mkdir -p /var/run/mysqld
    chown mysql:mysql /var/run/mysqld
    ln -s /var/lib/mysql/mysql.sock /var/run/mysqld/.
    The initial installation was done using The Perfect Server - CentOS 7.1 with some modification necessary for CentOS 7.2.
    I've noted that the /var/run/mysqld directory is deleted at each reboot. This was one reason that in the my.cnf file I'm using a more stable location for the mysql.sock file. I would think the update script should consult the my.cnf file to obtain the socket path.
    Is there something I can modify so that this problem won't happen the next time I need to update?

Share This Page