cPanel update blocked due to disk space available issue

[Jafar Muhammed]

Hello all,
I am getting this error notification.

cPanel & WHM cannot update due to insufficient disk space in the staging directory, '/usr/local/cpanel'. The system requires 3 GB to update; this directory only has 2.61 GB available. The system failed to find a new staging directory with enough space to update. You can either clear enough disk space or select a new staging directory with enough disk space at Update Preferences interface.

I had been receiving this notification when my version was 11.62.0.16, but I ignored the message. But Since today, I started getting this message. According to the notification, my cPanel version would be 11.62.0.15. But it is not.

The interesting part is at the top of WHM; I could see WHM 62.0 (build 17).
Under Update Preferences, it shows
Installed Version:62.0.17 Current Tier: stable.
I can see there are an 8+ GB available in Disk Usage section.

But still, I am getting this update blocker message.

 

[cPanelMichael]

I can see there are an 8+ GB available in Disk Usage section.

Hello,

Could you post the output from the "df -h" command on your system?

Thank you.

 

[Jafar Muhammed]

Here is the df-h output.

Filesystem Size Used Avail Use% Mounted on
/dev/vda1 20G 11G 8.2G 57% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
/usr/tmpDSK 681M 17M 629M 3% /tmp

 

[SysSachin]

Hello,

Try to make some free space on your server and run upcp again on your server. Check /var/log directory and remove old logs from your server.

 

[cPanelMichael]

Hello,

The output you provided suggests you have enough space to complete the cPanel update. Does the update proceed when running the "/scripts/upcp --force" command?

Thank you.

 

[Jafar Muhammed]

Hello @cPanelMichael @SysSachin, since a few days, I haven't received the blocker emails. I feel the issue is solved now (?).
May I reopen this thread or create another if again I happen to see them and close this now?

 

[cPanelMichael]

Hello @Jafar Muhammed,

Absolutely, feel free to reply to this thread if you encounter the same issue again.

Thanks!