MYSQL Server Failure

Discussion in 'ISPConfig 3 Priority Support' started by Bob Hall, May 25, 2016.

  1. Bob Hall

    Bob Hall New Member

    Hi There;
    I have installed and been using the tutorial version of ispconfig listed below and set up some websites for my users - all was working well until yesterday. for some reason the mysql database stopped working - i've done no updates on the system and aside from struggling a bit with the console language settings, had no problems previously. I've googled the issue (in phpmyadmin log on it states the controlfile is improperly configured, when stating the Db the error message is it failed: the control process failed with an error code. the log files are empty

    I know this is pretty vague but if you let me know what info to provide, I'll happily do it.

    thanks;
    bob
    ‚óŹ mysql.service - LSB: Start and stop the mysql database server daemon
    Loaded: loaded (/etc/init.d/mysql)
    Active: failed (Result: exit-code) since Wed 2016-05-25 14:29:05 CEST; 1min 34s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 14848 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

    May 25 14:28:34 ont-web1.tig.com mysqld[15024]: InnoDB: crash recovery and ignore that table.
    May 25 14:28:34 ont-web1.tig.com mysqld[15024]: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
    May 25 14:28:34 ont-web1.tig.com mysqld[15024]: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
    May 25 14:28:34 ont-web1.tig.com mysqld[15024]: InnoDB: and force InnoDB to continue crash recovery here.
    May 25 14:28:34 ont-web1.tig.com mysqld_safe[15038]: mysqld from pid file /var/run/mysqld/mysqld.pid ended
    May 25 14:29:05 ont-web1.tig.com mysql[14848]: ...fail!
    May 25 14:29:05 ont-web1.tig.com systemd[1]: mysql.service: Control process exited, code=exited status=1
    May 25 14:29:05 ont-web1.tig.com systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
    May 25 14:29:05 ont-web1.tig.com systemd[1]: mysql.service: Unit entered failed state.
    May 25 14:29:05 ont-web1.tig.com systemd[1]: mysql.service: Failed with result 'exit-code'.


    The Perfect Server - Ubuntu 15.10 (Wily Werewolf) with Apache, PHP, MySQL, PureFTPD, BIND, Postfix, Dovecot and ISPConfig 3
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you check if the harddisk is full? run as root user:

    df -h

    to check the harddisk space.
     
  3. Bob Hall

    Bob Hall New Member

    Hi There;
    Thanks for the quick response - the drive has 23gig free (output below)
    Filesystem Size Used Avail Use% Mounted on
    udev 982M 0 982M 0% /dev
    tmpfs 200M 9.1M 191M 5% /run
    /dev/dm-0 28G 3.6G 23G 14% /
    tmpfs 999M 0 999M 0% /dev/shm
    tmpfs 5.0M 4.0K 5.0M 1% /run/lock
    tmpfs 999M 0 999M 0% /sys/fs/cgroup
    /dev/sda1 236M 92M 132M 41% /boot
    tmpfs 200M 0 200M 0% /run/user/0
     
  4. Bob Hall

    Bob Hall New Member

    An interesting anomolie - I back up the vm with VEEAM each night the issue started yesterday but when I restored from Friday's backup, the mysql db problem appears in that backup however everything was fine at that time.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The error means that the InnoDB database file is broken and MySQl can not repair it without being forced to do that. It might be that the file was broken a few days ago and MySQL did not "recognize" it until it was restarted.

    Please try what the error message suggested and set innodb_force_recovery to e.g. 1 in the [mysqld] section of the my.cnf file and try to start MySQL again. Here is the procedure described at the MySQL website:

    http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
     

Share This Page