The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Maintenance ended; however, it did not exit cleanly (6400).

Discussion in 'General Discussion' started by dancingpony, Mar 29, 2016.

  1. dancingpony

    dancingpony Registered

    Joined:
    Mar 29, 2016
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brisbane, Australia
    cPanel Access Level:
    Root Administrator
    Hi,

    I've started receiving notifications (twice a day, 2 hours apart) each morning with the subject line "cPanel & WHM update failure in upcp script".

    I've pasted a copy of the end of the log file below. I can't quite see what the issue is though.

    Does the code '(6400)' mean anything?

    Code:
    [2016-03-23 05:41:50 +1000]   59% complete
    [2016-03-23 05:41:50 +1000]   Processing: Restoring compiler permissions
    [2016-03-23 05:41:50 +1000]    - Processing command `/usr/local/cpanel/scripts/compilers restore`
    [2016-03-23 05:41:50 +1000]      [28538] Compilers are enabled for unprivileged users.
    [2016-03-23 05:41:50 +1000]   60% complete
    [2016-03-23 05:41:50 +1000]   Processing: Cleaning up mailbox trash
    [2016-03-23 05:41:50 +1000]    - Processing command `/usr/local/cpanel/scripts/dovecot_auto_expunge_trash`
    [2016-03-23 05:41:50 +1000]   61% complete
    [2016-03-23 05:41:50 +1000]   Checking MySQL Version
    [2016-03-23 05:41:50 +1000]   MySQL version “5.0” is less than the recommended minimum version, “5.5”.
    [2016-03-23 05:41:50 +1000]   62% complete
    [2016-03-23 05:41:51 +1000]   65% complete
    [2016-03-23 05:41:51 +1000]   66% complete
    => Log closed Wed Mar 23 05:41:51 2016
    ----------------------------------------------------------------------------------------------------
    => Log opened from cPanel Update (upcp) - Slave (27102) at Wed Mar 23 05:41:51 2016
    [2016-03-23 05:41:51 +1000] E Maintenance ended, however it did not exit cleanly (6400). Please check the logs for an indication of what happened
    => Log closed Wed Mar 23 05:41:51 2016
    => Log closed Wed Mar 23 05:41:52 2016
    [2016-03-23 05:41:52 +1000]   95% complete
    [2016-03-23 05:41:52 +1000]   Running Standardized hooks
    [2016-03-23 05:41:52 +1000]   100% complete
    [2016-03-23 05:41:52 +1000]
    [2016-03-23 05:41:52 +1000]     cPanel update completed
    [2016-03-23 05:41:52 +1000]   A log of this update is available at /var/cpanel/updatelogs/update.1458675541.log
    [2016-03-23 05:41:52 +1000]   Removing upcp pidfile
    [2016-03-23 05:41:52 +1000]
    [2016-03-23 05:41:52 +1000] Completed all updates
    Cheers,
    BH-Tech
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Could you verify which version of MySQL is installed on this system? EX:

    Code:
    mysql --version
    The message quoted above suggests you are using an unsupported version of MySQL.

    Thank you.
     
  3. dancingpony

    dancingpony Registered

    Joined:
    Mar 29, 2016
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brisbane, Australia
    cPanel Access Level:
    Root Administrator
    The mysql version is 5.0.96

    However as the line says 'recommended', I wouldn't have thought this would hold up an update.

    Is this the issue?
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    It's a good idea to upgrade to a version of MySQL that is not end-of-life via:

    "WHM Home >> Software >> MySQL Upgrade"

    This option is documented at:

    MySQL/MariaDB Upgrade - Documentation - cPanel Documentation

    As for the update failure, the logs do not suggest a specific reason for the error message, so you can open a support ticket using the link in my signature if you would like us to take a closer look. Ensure you post the ticket number here so we can update this thread with the outcome.

    Thank you.
     
Loading...

Share This Page