turbo2ltr

Member
Jun 3, 2011
21
3
53
On Jun 1st my server tried to update to 11.30. I received an enormous email with the log in it. Here is the tail end of it.

Code:
[20110601.004632]      [8111] Done.
[20110601.004633]   ==> Starting cPanel....
[20110601.004633]    - Processing command `/usr/local/cpanel/etc/init/startup`
[20110601.004633]      [9376] Waiting for cpaneld to shutdown ... ...Done
[20110601.004633]      [9376] Waiting for webmaild to shutdown ... ...Done
[20110601.004633]      [9376] Waiting for cphulkd.pl to shutdown ... ...Done
[20110601.004633]      [9376] Waiting for cPhulkd to shutdown ... ...Done
[20110601.004633]      [9376] Waiting for cphulkd to shutdown ... ...Done
[20110601.004634]      [9376] [Wed Jun  1 00:46:33 2011] Current process '30251' stopped
[20110601.004634]      [9376] Waiting for cpdavd to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for cpdavd-ssl to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for cpdavd-ssl to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for cpldapd to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for cppop to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for cppop-ssl to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for cpanellogd to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for entropychat to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for eximstats to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for melange to shutdown ... ...Done
[20110601.004634]      [9376] Waiting for startmelange to shutdown ... ...Done
[20110601.004634]      [9376] Shutting down Mailman's master qrunner
[20110601.004635]      [9376] mailmanctl: no process killed
[20110601.004635]      [9376] Waiting for eximstats to shutdown ... ...Done
[20110601.004636]      [9376] Waiting for cpbandwd to shutdown ... ...Done
[20110601.004637]      [9376] [2011-06-01 00:46:37 -0700] [main] Current process '30218' stopped
[20110601.004637]      [9376] Waiting for tailwatchd to shutdown ... ...Done
[20110601.004637]      [9376] Graceful shutdown of cPanel TaskQueue Daemon requested. complete
[20110601.004637]      [9376] Waiting for cpsrvd to shutdown ... ...Done
[20110601.004637]      [9376] Waiting for cpsrvd-ssl to shutdown ... ...Done
[20110601.004637]      [9376] Waiting for whostmgrd to shutdown ... ...Done
[20110601.004637]      [9376] Waiting for cppop to shutdown ... ...Done
[20110601.004637]      [9376] Waiting for cppop-ssl to shutdown ... ...Done
[20110601.004637]      [9376] ==> cPanel TaskQueue Processing Daemon version 1.0
[20110601.004637]      [9376] [Wed Jun  1 00:46:37 2011] Starting /usr/local/cpanel/libexec/tailwatch/tailwatchd daemon
[20110601.004637]      [9376] Log is at /usr/local/cpanel/logs/tailwatchd_log
[20110601.004637]      [9376] Clearing main log /usr/local/cpanel/logs/cphulkd.log
[20110601.004637]      [9376] ==> cPanel Log Daemon version 25.0
[20110601.004637]    - Processing command `/usr/local/cpanel/whostmgr/bin/whostmgr2 --updateaddons`
[20110601.004638]      [9526] Updating addon type:modules addon:cronconfig version:0.4.1.......Done
[20110601.004638]      [9526] Updating addon type:modules addon:spamdconf version:0.5.......Done
[20110601.004638]      [9526] Locale database build scheduled.
[20110601.004638]   ==> Post Install Complete
[20110601.004638]    - Processing command `/usr/local/cpanel/cpkeyclt`
[20110601.004638]      [9536] Updating cPanel license...Done. Update succeeded.
[20110601.004638]      [9536] Building global cache for cpanel...Done
=> Log closed Wed Jun  1 00:46:38 2011
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave at Wed Jun  1 00:46:38 2011
[20110601.004638]   Post-sync cleanup completed successfully
[20110601.004638]
[20110601.004638]       cPanel update completed
[20110601.004638]   A log of this update is available at /var/cpanel/updatelogs/update.1306914002.log
[20110601.004638]
[20110601.004638] Completed all updates
=> Log closed Wed Jun  1 00:46:38 2011
Ever since then, whenever upcp runs, this is the only data it generates:

Code:
[20110602.004002]   Detected cron=1 (cron mode set from command line)
[20110602.004002]   Killing former upcp process "1205", starting new..
Notification => [email protected] via EMAIL [level => 1]
[20110602.004002]   Sending kill signal to process group for 1205
I also get an email:
Code:
/usr/local/cpanel/scripts/upcp was detected to be running as pid '30126'. Because it has been running for longer than 6 hours, the process will be killed and a new upcp will be run in it's place.

Any ideas on how to fix this?
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
41
348
somewhere over the rainbow
cPanel Access Level
Root Administrator
Could you both please open up a ticket for us to investigate this thoroughly? You can use WHM > Support Center > Contact cPanel or using the link in my signature. Please post the ticket numbers here upon opening them.
 

turbo2ltr

Member
Jun 3, 2011
21
3
53
Ticket 1572773

I was going to upload the log, but I don't see any place to upload in the ticket. I don't want to upload it publicly.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
41
348
somewhere over the rainbow
cPanel Access Level
Root Administrator
You should simply be able to reply to the ticket via email and attach the file in your reply. Otherwise, the ticket system should have an option to attach if you log into it.
 

garconcn

Well-Known Member
Oct 29, 2009
172
18
68
My server has finished the upgrade after a few hours(3-6 hours). But I saw it has weird characters in WHM Update Preferences section:

CURRENT (“release candidateâ€)
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
41
348
somewhere over the rainbow
cPanel Access Level
Root Administrator
Was a ticket submitted as previously requested? Thanks!

For the ticket that was submitted (1572773), the upcp was failing due to a customized upcp cron command with a sed being passed in it to a log file location. When the command was changed to be the default upcp for 11.30, the upcp succeeded for the cron. The default cron path command for 11.30 cPanel is the following:

Code:
/usr/local/cpanel/scripts/upcp --cron
The time interval would be placed before the command path, so I'm only noting the change in path from "/scripts/upcp" to "/usr/local/cpanel/scripts/upcp --cron" from 11.28 to 11.30 along with the fact that other machine had a customized cron being used.
 

larry2148

Member
Aug 16, 2006
6
0
151
I'm having the same issue, I have the following strange characters in the update preferences area:
Code:
CURRENT (“release candidateâ€)
my current crontab for upcp is:
Code:
17 0 * * * /scripts/upcp
(has not been customized to my knowledge)

Would you have any clues as to why this is going on? I'm getting these emails the past few days:

Code:
/usr/local/cpanel/scripts/upcp was detected to be running as pid '26377'. Because it has been running for longer than 6 hours, the process will be killed and a new upcp will be run in it's place.
Thanks in advance,
Larry
 
Last edited:

cPanelNick

Administrator
Staff member
Mar 9, 2015
3,481
35
208
cPanel Access Level
DataCenter Provider
I'm having the same issue, I have the following strange characters in the update preferences area:
Code:
CURRENT (“release candidateâ€)
my current crontab for upcp is:
Code:
17 0 * * * /scripts/upcp
(has not been customized to my knowledge)

Would you have any clues as to why this is going on? I'm getting these emails the past few days:

Code:
/usr/local/cpanel/scripts/upcp was detected to be running as pid '26377'. Because it has been running for longer than 6 hours, the process will be killed and a new upcp will be run in it's place.
Thanks in advance,
Larry
This is a generic message that means the previous update failed to be complete. It could indicate any number of problems. The most common we see is a corrupt rpm database. We should be able to get you all sorted out if you open a ticket at https://tickets.cpanel.net/submit/ so we can take a look.
 

ednilson

Member
Jun 3, 2011
8
0
51
I'm also having problems, I installed cpanel on June 2. Yesterday I received this email

Subject: Cpanel update failure in upcp

Post-sync cleanup has ended, however it did not exit cleanly. Please check the logs for an indication of what happened
 

ednilson

Member
Jun 3, 2011
8
0
51
I tried to update now with the command /scripts/upcp and it worked, before he stopped at a certain part and never actualized.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
41
348
somewhere over the rainbow
cPanel Access Level
Root Administrator
The cPanel update logs are located in /var/cpanel/updatelogs/ location and can be determined which is newest based on timestamp with an "ls -lah /var/cpanel/updatelogs" command. It would be great to have the log details when an upcp fails so we can see what the log is specifically showing.

Otherwise, the best idea would be to open up a ticket with us using WHM > Support Center > Contact cPanel or using the link in my signature.