Skip to main content

Cpanel Update Failing

nootkan
After migrating from centos 7.9 to alma linux 8.8, I've been dealing with a lot of issues it seems with configuration. Some of which have been resloved by cPRex and the great people at support. Recently I've been seeing this error in my logs and have been researching on cPanel forum for a solution but nothing I've tried seems to work. Tried forcing the update with [quote]/scripts/upcp --force
and that failed also. Here is a copy of the results: [quote] /scripts/upcp --force [2023-10-29 19:00:23 -0700] Detected cron=0 (--force passed on command line) ---------------------------------------------------------------------------------------------------- => Log opened from cPanel Update (upcp) - Slave (1162928) at Sun Oct 29 19:00:23 2023 [2023-10-29 19:00:23 -0700] Detected cron=0 (--force passed on command line) [2023-10-29 19:00:23 -0700] 1% complete [2023-10-29 19:00:23 -0700] Running Standardized hooks [2023-10-29 19:00:23 -0700] 2% complete [2023-10-29 19:00:23 -0700] mtime on upcp is 1694188171 (Fri Sep 8 08:49:31 2023) ---------------------------------------------------------------------------------------------------- => Log opened from /usr/local/cpanel/scripts/updatenow (1162930) at Sun Oct 29 19:00:23 2023 [2023-10-29 19:00:23 -0700] Running version '11.114.0.8' of updatenow. [2023-10-29 19:00:23 -0700] E The install encountered a fatal error: (XID 2qrmw6) The system failed to create the temporary file "/var/tmp/1162930._USR_LOCAL_CPANEL_SCRIPTS_UPDATENOW__.tmp.0eb25b35" because of an error: No such file or directory => Log closed Sun Oct 29 19:00:23 2023 [2023-10-29 19:00:23 -0700] 17% complete [2023-10-29 19:00:23 -0700] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1162928.15749134.1698473731.log --force` failed, exited with code 255 (signal = 0) => Log closed Sun Oct 29 19:00:23 2023 => Log closed Sun Oct 29 19:00:24 2023
Any help much appreciated.

Comments

8 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! What do you see when you run this command? ls -ld /var/tmp I would expect the output to look like this on an AlmaLinux 8 system: drwxrwxrwt. 15 root root 4096 Oct 30 12:36 /var/tmp If so, can you try manually creating a file in there to see if that works? touch /var/tmp/testfile
    0
  • nootkan
    [quote] Hey there! What do you see when you run this command? ls -ld /var/tmp I would expect the output to look like this on an AlmaLinux 8 system: drwxrwxrwt. 15 root root 4096 Oct 30 12:36 /var/tmp If so, can you try manually creating a file in there to see if that works? touch /var/tmp/testfile
    Hi cPRex, here is what I see when running those commands: [quote]# ls -ld /var/tmp drwxrwxrwt 0 root root 0 Oct 27 23:15 /var/tmp [root@me ~]# touch /var/tmp/testfile touch: cannot touch '/var/tmp/testfile': No such file or directory
    0
  • cPRex Jurassic Moderator
    Well, that's something. What about this command? lsattr -d /var/tmp
    0
  • nootkan
    cPRex, here is the result: [quote] # lsattr -d /var/tmp --------------e----- /var/tmp
    I decided to open a support ticket as once again I am stumped. Seems to be a theme with me and Alma Linux. And I was just starting to understand Centos.
    0
  • cPRex Jurassic Moderator
    I wouldn't normally expect that -e to be present. Here are some details on what that does:
    0
  • nootkan
    cPRex, thanks for your reply. Support says I need to unmount /tmp and secure it again which I tried by running [quote]unmount /tmp
    but recieved the following: [quote] # umount /tmp umount: /tmp: target is busy.
    After some research into "target is busy" I found this link: Fixing 'Umount Target is Busy' Error in Linux. which gives three options to unmount the target (in this case tmp) but not sure which one to use. I ran the following command from the first option [quote]sudo lsof /var/tmp
    . That gave me many lines of code which looks to me like there are many processes running but can't be sure as I am not comfortable with what I am reading. Too many lines to add here for you to see. I gave support all the steps I have taken up to now and will wait until tonight when they reply to see what they suggest I do. Do you have any idea what could cause the tmp file to become corrupt so it cannot be written to? It wasn't doing this until last Sunday morning when I noticed it, but up until then my cp updates were working fine. Does this happen on its own or is it something I may have done inadvertantly while trying to resolve the other issues with Alma Linux on my new server? Thanks again for your support.
    0
  • cPRex Jurassic Moderator
    I can't say for sure what would cause such a thing to happen, but this would be something to bring up with the host itself as they could scan the hardware or drive for any issues. Hopefully they'll have a good reply to send you, as this indicates issues at a deeper level than the cPanel tools.
    0
  • nootkan
    cPRex, thanks. I am the host as this is my own dedicated server. I'll let you what support tells me.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post