cPanel maintenance is already running?

[arhs]

Hi,

I am getting the following message when trying to update cPanel.

[20110527.083824] 0% complete [20110527.083824] Detected cron=0 (manual flag passed on command line) [20110527.083824] E cPanel maintenance is already running. Please wait for the previous maintenance to complete, or kill off all maintenance processes and try again.

I have tried killall -9 upcp and nothing happens.

[cpanelkenneth]

Look for a process named maintenance. In 11.30 many of the tasks formerly performed by upcp are now handled by one of several different scripts. These scripts are run as child processes of upcp. updatenow and maintenance are two such scripts.

[arhs]

Got it working now. Thanks :-)

[PenguinInternet]

I've just had this issue and gone around in circles trying to find a maintenance process that didn't exist. It turns out that the update script appears to only be looking for the word maintenance anywhere in the process list and got caught by:

/usr/lib/courier-imap/bin/imapd /home/someuser/mail/someusermaintenance.co.uk/mailuser

Obviously full details replaced for privacy. Once the process was killed the upgrade proceeded. Can you raise this as a bug Kenneth or should I do this via a ticket?

[cpanelnick]

Can you raise this as a bug Kenneth or should I do this via a ticket?

case 50290 has been opened to track this.

[stdout]

I just experienced the same problem.
A user's PHP process contained "maintenance" in it's name - cPanel was failing to update.
I had to kill it off in order to "upcp". I just hope the script doesn't impact our customer's website in any way.

I had a similar issue yesterday where I started a screen session titled "easyapache" (for the client's convenience) - the easyapache script wouldn't start because cPanel thought easyapache was already running.

Please use more specific process checks.

[cPanelTristan]

Cases 50290 and 50298 (the backport for 11.30) should already have been resolved. The 50298 case was built for 11.30.0.27 or higher. If you are still having this happening when "maintenance" is in a PHP process name, please submit a ticket for us to investigate this further.