Hi,
not sure if this is a bug or if it belongs to Iworx/NodeWorx/SiteWorx or OS so I post here.
Centos 4.1 is our distro.
There seems to be no quota set on our SiteWorx accounts.
In NodeWorx -> SiteWorx -> Accouts, all are listed as having used 0 MB.
When a SiteWorx account clicks on Disk Space (…siteworx/stats.php?mode=realtime&graph=storage) from their main page, it gets them to an empty page.
If I run “quota -gs <username>” it returns for all accounts:
Disk quotas for group <groupname> (gid <id>): none
On the initial install I prepared /home with quota settings as per the install documentation:
and ran “/home/interworx/cron/storage.pex” as the iworx user
In NodeWorx the SiteWorx accounts page now shows used space.
From SiteWorx the empty page remains though, when clicking on Disk Space!
A “quota -gs <username>” still says “… none”
A “repquota /home” displays:
*** Report for user quotas on device /dev/mapper/rootvg-homelv
Block grace time: 7days; Inode grace time: 7days
Block limits File limits
User used soft hard grace used soft hard grace
I’m also a bit curious as to where the SiteWorx users databases should be located?
Our SiteWorx user db’s are located under /var/lib/mysql/ but I can see directories called /home/<account>/var/<domain>/database/
Where should they be located exactly?
If they should be under /var/lib/mysql, is NodeWorx calculating the quota for the db’s aswell when “partition” in iworx.ini is set to /home ?
I’m also a bit curious as to where the SiteWorx users databases should be located?
Our SiteWorx user db’s are located under /var/lib/mysql/ but I can see directories called /home/<account>/var/<domain>/database/
Where should they be located exactly?
If they should be under /var/lib/mysql, is NodeWorx calculating the quota for the db’s aswell when “partition” in iworx.ini is set to /home ?
The should be in /var/lib/mysql which is the default MySQL spot. If you change user quotas to use /home the DBs in /var won’t be included in the quota’d total tsl.
OK, I changed it back to partitions="/home" and ran the quota checks again. Now NodeWorx shows used space, but I don’t believe the space used for the users db’s are included…right?! So how is this controlled?
[root@box home]# repquota -g /home
*** Report for group quotas on device /dev/mapper/rootvg-homelv
Block grace time: 7days; Inode grace time: 7days
Block limits File limits
Group used soft hard grace used soft hard grace
Opps, this is not good!
It could be that we get customers with huge databases and they are still under their NodeWorx limits due to small web and email content.
What if I move mysql to somewhere under /home and create a symlink?
Something like:
[/var/lib] # ln -s /home/db/mysql mysql
That would probably work with the quotas i guess (or hope). Would Iworx-CP have any problems with this setup?
It could be that we get customers with huge databases and they are still under their NodeWorx limits due to small web and email content.
yep ;).
Something like:
[/var/lib] # ln -s /home/db/mysql mysql
quotas are partition based so symlinks across partitions won’t fix the issue tsl. The best solution is to copy your /var/lib/mysql to /home and then symlink from /var/lib/mysql => /home/mysql for example.
I was under the assumption that quotas were handled by the group name associated with files anywhere on the server root filesystem? Although even if that is true I guess that the mysql files are mysql:mysql so that wouldn’t help either.
For some reason i thought the mysql data was counted :rolleyes:
What would happen if I changed the group on the /var/lib/mysql files to the group which they belong and leave the owner alone would that make a difference?
quotas are partition based so symlinks across partitions won’t fix the issue tsl. The best solution is to copy your /var/lib/mysql to /home and then symlink from /var/lib/mysql => /home/mysql for example.
Yes, thats what I meant
Justec,
the MySQL db files created by the users gets
mysql:<groupname>
So quotas should work, if not on separate partitions.