Maintenance ended; however, it did not exit cleanly

Hello i'm getting this error email from my server. Which states cPanel & WHM update failure in upcp script



The cPanel & WHM update process failed for the following reason:


Maintenance ended; however, it did not exit cleanly (512). Review the update logs to determine why the update failed.



Update log preview:
[2016-11-30 01:57:11 -0400] [30885] Restarting Apache
[2016-11-30 01:57:12 -0400] - Processing command `/usr/local/cpanel/scripts/check_mount_procfs`
[2016-11-30 01:57:12 -0400] 81% complete
[2016-11-30 01:57:12 -0400] - Processing command `/usr/local/cpanel/scripts/setup_modsec_db`
[2016-11-30 01:57:12 -0400] - Processing command `/usr/local/cpanel/scripts/modsec_vendor update --auto`
[2016-11-30 01:57:12 -0400] 82% complete
[2016-11-30 01:57:12 -0400] - Processing command `/usr/local/cpanel/bin/check_cpstore_in_sync_with_local_storage`
[2016-11-30 01:57:12 -0400] Processing: Purging old comet files
[2016-11-30 01:57:12 -0400] - Processing command `/usr/local/cpanel/bin/purge_dead_comet_files --quiet`
[2016-11-30 01:57:12 -0400] 83% complete
[2016-11-30 01:57:12 -0400] Processing: Restoring compiler permissions
[2016-11-30 01:57:12 -0400] - Processing command `/usr/local/cpanel/scripts/compilers restore`
[2016-11-30 01:57:13 -0400] [30989] Compilers are enabled for unprivileged users.
[2016-11-30 01:57:13 -0400] 84% complete
[2016-11-30 01:57:13 -0400] Processing: Cleaning up mailbox trash
[2016-11-30 01:57:13 -0400] - Processing command `/usr/local/cpanel/scripts/dovecot_maintenance --background`
[2016-11-30 01:57:13 -0400] MySQL version "10.1" is greater than or equal to the recommended minimum version, "5.5".
[2016-11-30 01:57:13 -0400] 85% complete
[2016-11-30 01:57:13 -0400] 86% complete
[2016-11-30 01:57:13 -0400] 87% complete
[2016-11-30 01:57:13 -0400] Removing expired entries from ModSecurity's IP persistence storage.
=> Log closed Wed Nov 30 01:57:13 2016
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (28036) at Wed Nov 30 01:57:13 2016
[2016-11-30 01:57:13 -0400] E Post Maintenance ended, however it did not exit cleanly (512). Please check the logs for an indication of what happened

So this is part of the error logs.


[2016-11-30 00:39:52 -0400] info [purge_modsec_log] Purged stale records from modsec database.
[2016-11-30 00:39:53 -0400] info [checkerrorlogsafe] Adding error_log exclusion to Apache configuration
[2016-11-30 00:39:58 -0400] info _archive_maintenance] Email archiving is disabled per Tweak Settings.
[2016-11-30 00:39:59 -0400] warn [updatephpconf] Unable to locate php.ini in directory /usr/local at /usr/local/cpanel/Cpanel/PHPINI.pm line 891.
   Cpanel::PHPINI::update_config("/usr/local") called at /usr/local/cpanel/scripts/updatephpconf line 47
[2016-11-30 00:40:00 -0400] info [setup_modsec_db] Initialized ModSecurity" database.
[2016-11-30 00:40:00 -0400] info [modsec_vendor] Updates are in progress for all of the installed ModSecurity vendors with automatic updates enabled.
[2016-11-30 00:40:01 -0400] info [cPanel] upcp::MaintenanceFailed Notification => ryan_kemraj_persad@hotmai***** via EMAIL [eventimportance => High (1)]
==> cpsrvd 11.61.9999.82 started
==> cpsrvd: loading security policy....Done
==> cpsrvd: Setting up SSL support ... Done
==> cpsrvd: transferred port bindings
==> cpsrvd: bound to ports
OK
[2016-11-30 00:56:55 -0400] info [dav_change_hostname] The system will now change the calendar and address book hostnames from "server.example.com" to "server.example.com".
[2016-11-30 00:56:55 -0400] info [dav_change_hostname] Temporarily disabling quota for centralneon on /dev/vda1: (was 1024000/1024000 soft/hard blocks and 0/0 soft/hard inodes)


DID try killall upcp
killall -9 upcp
/scripts/upcp.static --force

Same problem, Btw i'm using the latest edge built.

Kelli

November 30, 2016 13:18

Hi Kemraj! We've recently introduced a maintenance script (which calls modsec-sdbm-util) to manage db bloat caused by ModSecurity. The error you experienced is caused when there are no db files to check, which we had missed in our development. We have a fix for this in test right now, and will have this resolved in v62 very soon!

kemraj

November 30, 2016 15:01

Thank you very much again for the great support, now i don't need to stress about this. I taught it was a fault of my own.

December 09, 2016 13:52

Good Morning! The fix will appear in builds 11.61.9999.96 and later.

Maintenance ended; however, it did not exit cleanly

Comments

Didn't find what you were looking for?