- Troubleshooting Quotas
- The quotas on my SiteWorx accounts aren't updating or showing correctly. What should I do?
- Why aren't my databases counting toward my disc quota?
- Can a corrupted quota crash my server?
- I tried to create a SiteWorx account and the error log says "error changing quotas" (or something similar). What's up?
- I'm running a VPS and aquota.group and aquota.user are missing. What's wrong?
Troubleshooting Quotas
The quotas on my SiteWorx accounts aren't updating or showing correctly. What should I do?
First run a quota check
quotacheck -cugvmf -F vfsv0 /
If your home directory is in your root partition
quotacheck -cugvmf -F vfsv0 /home
if the /home directory is also a partition
quotacheck -cugvmf -F vfsv0 /chroot
if you are set up for jailed shells and the /chroot directory is also a disk partition
Then run:
~iworx/cron/storage.pex
Your quotas should be correct now.
Why aren't my databases counting toward my disc quota?
If you split MySQL storage and web content storage onto 2 physical disk partitions then there is no way to track both under the account’s storage umbrella.
It is possible that server administrators get customers with huge databases, but stay under the disk quota specified in NodeWorx due to small web and email content. There is no supported way around this. The best option we’ve seen is to copy your /var/lib/mysql to /home and then symlink from /var/lib/mysql => /home/mysql (for example). Quotas are partition based so symlinks across partitions won’t fix the issue, the files must physically be moved.
Can a corrupted quota crash my server?
No, the only obvious symptom of a corrupted quota is that NodeWorx will show all SiteWorx accounts set to 0.00 MB. Users going over storage quota should not cause a server to crash, unless there are other underlying issues. The worst thing that the support team has seen is that IMAP can cause high loads if the user’s mailbox quota is exceeded.
I tried to create a SiteWorx account and the error log says "error changing quotas" (or something similar). What's up?
Sep 23 00:46:40 package.activate.php [info] setting permissions on: /home/awtrorg Sep 23 00:46:40 package.activate.php [info] setting quotas for: awtrorg to 999999999 MB Sep 23 00:46:40 package.activate.php [info] /usr/sbin/setquota -g awtrorg 0 0 0 0 / Sep 23 00:46:40 package.activate.php [error] error changing quotas: awtrorg Sep 23 00:46:40 package.activate.php [error] activating package: awtrorg: failed Sep 23 00:46:40 package.activate.php [info] script end Sep 23 00:46:40 iworx [info] siteworx: deactivating package: awtr.org
Your quotas are not working for some reason.
If you are on a VPS, your provider may have turned off quotas in Virtuozzo for some reason. You will need to contact your VPS provider’s support department to get this turned on. They will need to shut down the VPS to do it so you will save time if you give them permission to do so in the initial request.
If you are running a dedicated server, you should run a quotacheck:
quotacheck -cugvmf -F vfsv0 /
If your home directory is in your root partition
quotacheck -cugvmf -F vfsv0 /home
if the /home directory is also a partition
quotacheck -cugvmf -F vfsv0 /chroot
if you are set up for jailed shells and the /chroot directory is also a disk partition
Then run:
~iworx/cron/storage.pex
Your quotas should be correct now.
I'm running a VPS and aquota.group and aquota.user are missing. What's wrong?
Nothing, this is normal for Virtuozzo VPS‘s. Virtuozzo handles their functions in the background. There is no real loss, the files are gibberish (to your text editor anyway) so you can’t edit them manually anyway.
