[MySQL & i-MSCP] Error after upgrade to 1.1.17

  • Hi!


    I upgraded i-MSCP to 1.1.17 this morning (08:40). I did do a quick test run this morning too, on a seperate server, but no errors there (yet).
    Both installations went fine, no errors found (in log files/during installation) what so ever.


    After about 3 hours I received some exceptions via e-mail, I pasted them on pastebin:
    1. http://pastebin.com/Gx4w3b9x
    2. http://pastebin.com/CKJZMyg6
    There are about 4 more identical e-mails.


    Some meta-information
    The upgrade was from 1.1.16 to 1.1.17.

    Code
    1. # cat /proc/version
    2. Linux version 3.10.11 (root@***) (gcc version 4.4.5 (Debian 4.4.5-8) )


    Checked the setup log, no abnormal exit codes or error codes found in it, ended nicely with http://pastebin.com/GtVD4bg3


    The websites do work, the control panel seems to work too (no visible errors as of this moment), it's just those emails with strange exceptions.

  • Hello ;


    • Distro in use?
    • SQL server in use?
    • SQL server log (from syslog)
    • You /etc/mysql/my.cnf content?
    • phpinfo() result?


    You should really consider to read the posting rules again ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Also please, the phpinfo() result (from i-MSCP site). I thinks about a mysqld socket path problem there or something like that.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • About that socket, it does exsist:
    # stat /var/run/mysqld/mysqld.sock
    File: `/var/run/mysqld/mysqld.sock'
    Size: 0 Blocks: 0 IO Block: 4096 socket
    Device: dh/13d Inode: 1109477 Links: 1
    Access: (0777/srwxrwxrwx) Uid: ( 107/ mysql) Gid: ( 113/ mysql)
    Access: 2014-11-17 08:40:13.653044118 +0100
    Modify: 2014-11-17 08:40:13.115043623 +0100
    .Change: 2014-11-17 08:40:13.115043623 +0100

  • What is the value of the DATABASE_HOST parameter in your /etc/imscp/imscp.conf file ? Also, please post your /etc/hosts file (in private)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Re;


    I don't see anything wrong here. Anyway, if the panel is working now, this simply means that those exceptions occured during the i-MSCP update. You are not showing the datetime of those mails so... Those exceptions are only thrown when the panel cannot connect to the i-MSCP database, which is not the case ATM.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206