Unable to complete cPanel Update (upcp)
Unable to complete cPanel Update ...failed, exited with code 255 (signal = 0)
Hi,
Update does not complete currently stuck at WHM 11.46.0 (build 15). Below is the log of the event.
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (202939) at Sat Nov 22 09:20:52 2014
[20141122.092052] Detected cron=1 (env var CPANEL_IS_CRON was present before this process started.)
[20141122.092052] 1% complete
[20141122.092052] Running Standardized hooks
[20141122.092052] 2% complete
[20141122.092052] mtime on upcp is 1415179162 (Wed Nov 5 01:19:22 2014)
----------------------------------------------------------------------------------------------------
=> Log opened from /usr/local/cpanel/scripts/updatenow (202943) at Sat Nov 22 09:20:53 2014
[20141122.092053] Detected version '11.46.0.15' from version file.
[20141122.092053] Running version '11.46.0.15' of updatenow.
[20141122.092053] Using mirror '74.50.120.123' for host 'httpupdate.cpanel.net'.
[20141122.092053] Target version set to '11.46.0.17'
[20141122.092053] Switching to 11.46.0.17 to determine if we can reach that version without failure.
[20141122.092053] Retrieving and staging /cpanelsync/11.46.0.17/cpanel/scripts/updatenow.static.bz2
[20141122.092053] Using mirror '208.109.109.239' for host 'httpupdate.cpanel.net'.
[20141122.092053] Set permissions on /usr/local/cpanel/scripts/updatenow.static-cpanelsync to 0700
[20141122.092053] Become an updatenow.static for version: 11.46.0.17
=> Log closed Sat Nov 22 09:20:53 2014
----------------------------------------------------------------------------------------------------
=> Log opened from /usr/local/cpanel/scripts/updatenow.static-cpanelsync (202943) at Sat Nov 22 09:20:54 2014
[20141122.092054] Detected version '11.46.0.15' from version file.
[20141122.092054] Running version '11.46.0.17' of updatenow.
[20141122.092054] Using mirror '208.109.109.239' for host 'httpupdate.cpanel.net'.
[20141122.092054] Target version set to '11.46.0.17'
[20141122.092054] Checking license
[20141122.092054] License file check complete
=> Log closed Sat Nov 22 09:20:54 2014
[20141122.092054] 17% complete
[20141122.092054] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1416676852.log` failed, exited with code 255 (signal = 0)
=> Log closed Sat Nov 22 09:20:54 2014
-
Hello :) Please open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you. 0 -
]Hello :) Please open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you.
Here is the ticket# 57373330 -
To update, this occurred because new files could not be written to the /var/tmp directory. The user remounted /var/tmp to address the issue. Thank you. 0 -
]To update, this occurred because new files could not be written to the /var/tmp directory. The user remounted /var/tmp to address the issue. Thank you.
Hi Michael :D, I have the same problem (Ticket ID #5843845). Eric from cPanel advised me that this is a System Admin issue... The server is about 2 week old and only have one big site running on it, I can't see what could have cause this :confused:, but from Eric test : [10:07:00 web root@5843845 /var/tmp]cPs# touch somefile touch: cannot touch `somefile': No space left on device [10:07:05 web root@5843845 /var/tmp]cPs#
I can only assume that remounting the /var/tmp will solve the issue (finger are cross!) Could you just guide me on how to remount the drive :D ? Thank you!0 -
You could try running the following command: /scripts/securetmp
Enter "Y" when it asks if you "Would you like to secure /tmp & /var/tmp now?". Let us know if it helps. Thank you.0 -
Thank you Michael, Unfortunatly this didn't do the trick, I've still got the same error while trying to update CP. The script you've suggested did mentioned that the /tmp & /var/tmp was already secured. 0 -
Please report that issue to your hosting provider/data center, or a qualified system administrator. It's likely going to require some manual changes to the /var/tmp partition on your system. Thank you. 0
Please sign in to leave a comment.
Comments
7 comments