cgroups isloates resources by accounts. So this has to be done for all users and virtual hosts if required.
If you set a CPUQuota of 10% for a user, all accesses by the user must not exceed 10%. This includes those in OLS and user login sessions. All will be shared fairly by the operating system. If you start more processes, the total percentage for the user does not change, but each process runs a bit slower so as to avoid monopolizing the CPU.
Again Inodes uses increased by 3% without hosting any domain. When Inodes was 100% uses, I’m not able to do any thing then i faced server error 505. After that I increased volume stroage by 10GB then Inodes changed to 100% uses to 86% uses. But, again it was increasing automatically. I’m afraid now because how much storage i have to increase. Because when i check storage uses then its shows only 37% uses, 63% is waist and i haved to pay for 63% storage.
I increased 30Gb one by one because Inodes was always full in few days after incresing the volume. This is very serious issue. I will provide you the screenshot of list of files which is using most Inodes. The in left side of file name is Inodes uses.
Now Inodes uses increase by 3% more. Means in few hours Inodes uses increased by 6% and after some time Inodes was full and again I’m in big trouble because, when Inodes was full I’m not able to do any things. After that it will again gives me server error 500 while opening 8090 port. This is big issue, I’m very afraid about this issue. I already increased 30 to 40 Gb in few weeks because of Inodes issue. But, still I’m facing this issue. Do you please check why this problem was happening.
I hope you will understand my situation. After few hours Inodes uses become full and I’m not able to do anything. I’m deleted many wordperss sites but still it Inodes uses was increasing.
It should have many of those files, because devs never correctly set up the clean of sessions (last time I checked).
If that’s the case, I will post the fix here (but you will need to re-apply every time you update cyberpanel)
# Reload systemd manager configuration. This will rerun all generators (see systemd.generator(7)), reload all unit files, and recreate the entire dependency tree. While the daemon is being reloaded, all sockets systemd listens on behalf of user configuration will stay accessible.
systemctl daemon-reload
systemctl restart lsws
