failing ucp

izghitu

• January 21, 2015 07:12

Hi, Running /scripts/upcp on CentOS 5.11 fails with this:
[20150121.080806] E Could not put new '/usr/local/cpanel/.cpanelsync_binaries__forward_slash__linux-x86_64' into place from /usr/local/cpanel/.cpanelsync_binaries__forward_slash__linux-x86_64-cpanelsync: No such file or directory [20150121.080806] The Administrator will be notified to review this output when this script completes [20150121.080806] E Detected events which require user notification during updatenow. Will send iContact the log [20150121.080806] Removing staged files and directories for binaries/linux-c5-x86_64, cpanel [20150121.080806] Removing staged files and directories for x3 [20150121.080806] Removing staged files and directories for x3mail
Can't find anything on google. Please help

• 

  cPanelMichael

  • January 21, 2015 16:58

  Hello :) Please check to see if the following script completes successfully:
  /scripts/check_cpanel_rpms
  Thank you.

  0
• 

  serversurgeon

  • January 21, 2015 18:10

  Hi Michael, Thanks for the suggestion. That fixed the problem.
  # /scripts/check_cpanel_rpms Problems were detected with cPanel-provided files which are RPM controlled. If you did not make these changes intentionally, you can correct them by running: > /usr/local/cpanel/scripts/check_cpanel_rpms --fix The following files were found to be altered from their original RPM: cpanel-php54-Horde-Core,2.8.0,1.cp1142 cpanel-php54-Horde-Editor,2.0.3,1.cp1142 cpanel-php54-Horde-Mime-Viewer,2.0.5,1.cp1142 cpanel-php54-content,2.0.3,1.cp1142 cpanel-php54-horde,5.1.4,1.cp1142 cpanel-php54-imp,6.1.4,4.cp1142 cpanel-php54-ingo,3.1.2,3.cp1142 cpanel-php54-kronolith,4.1.3,3.cp1142 cpanel-php54-mnemo,4.1.1,1.cp1142 cpanel-php54-nag,4.1.2,1.cp1142 cpanel-php54-timeobjects,2.0.4,1.cp1142 cpanel-php54-trean,1.0.3,1.cp1142 cpanel-php54-turba,4.1.2,1.cp1142 cpanel-php54-webmail,5.1.1,1.cp1142 Do you want to repair these RPMs?(y/n):y
  

  0
• 

  cPanelMichael

  • January 21, 2015 18:55

  I am happy to see the issue is now resolved. Thank you for updating us with the outcome.

  0

Please sign in to leave a comment.