[Mashiro]

@Littlemaster

OP has a OpenVZ VPS and thus he cannot have the same issues described in the topics you linked to. OpenVZ containers have no own kernel and therefore also no real boot partition where the kernel files could be stored to be filled up.

Mind the path in the error messages. It is not even the boot partition with the kernel files that is the issue in this case. It is the /var folder in the OpenVZ root filesystem. That's a major failure on some side.


@youssefbasha

Just because the control panel of your VPS says you have over 100 GB free disk space it doesn't mean you really have it! You're running on a OpenVZ VPS that gets no real reports from the host OS about real disk usage on the node.

What does it mean for you? The host node could be full while your VPSs only uses a small bit of space of your allowance. OpenVZ allows overselling without limits on CPU, RAM, disk space and network. So if the host node disk is full your VPS cannot really see this.

What happens? Despite your VPS showing free disk space you don't really have any free disk space left. Thus your updates, installations and so on will fail.


Another sign of a full host node disk is when you have a high usage percentage of disk space in "df -h" output even though you only used a small bit.

e.g: You have a 100 GB disk. You used 10 GB (10%) of it really. You run a report with df -h and it says the following:
Used: 10 GB (99%)
Free: 90 GB (1%)
Total: 100 GB

In the example above the host node disk is so full that nothing fits into it anymore and your free 90 GB become absolutely useless because you cannot use them.

Welcome to the world of massively overselling providers, bad performance, downtime and a lot of fun.