Hello,
You'll have to excuse me if this has already been brought to light..
Quotas never really used to be a problem. I guess DirectAdmin only checks quotas every so often. So when accounts fill up, gameservers would stop working because they cant produce output. Normally what I would do is just clear out some logs or increase the account space.
If I cleared logs, DirectAdmin would still display the account as being full, but the gameservers would run and output just fine because there was infact, real space available there. There were times where DirectAdmin would need to have a bit of a refresher to register the new space being there. By doing a search I found the solution to this. It would work, and is found here:
http://help.directadmin.com/item.php?id=39
If I increased the account size instead of clearing files, DirectAdmin would reflect the change imediately. (although I suspect it didnt update the actual space used, just the new limit)
Well now one of the accounts seems to be stuck. Inside directadmin itself, it says they are using 15.9mb / 90mb after clearing some of their logs and following the instructions at the link above. However, if I go back and do the quota -v username it still says they are over 90mb after the tally and the account isnt linked to any extra files.
I am hoping it will correct itself when DirectAdmin does its normal thing.. but this is kinda bad because his server kept refusing to run because it couldnt output any logs and I had no idea what the problem was.
I just increased it to 100, then to 120. Each time I do the quota is always the same as the limit. Also, the heading called blocks always steadily increases. Im talking like +1000 within 1 second until it reaches the same as the limit and then it has a * next to it.
[root@fracnet public_12]# quota -v snag
Disk quotas for user snag (uid 503):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 121512 122880 122880 219 0 0
[root@fracnet public_12]# quota -v snag
Disk quotas for user snag (uid 503):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 122064 122880 122880 219 0 0
[root@fracnet public_12]# quota -v snag
Disk quotas for user snag (uid 503):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 122880* 122880 122880 219 0 0
This is the output from when I executed the quota command 3 times, in under two seconds total. Just after I increased it to 120mb from 100mb.
Any ideas? Feedback appreciated
Oh yeah, and I am using the newest DirectAdmin (updated it today after having this problem) and I am using CentOS but DirectAdmin says its Redhat. Maybe it is
-Chi
You'll have to excuse me if this has already been brought to light..
Quotas never really used to be a problem. I guess DirectAdmin only checks quotas every so often. So when accounts fill up, gameservers would stop working because they cant produce output. Normally what I would do is just clear out some logs or increase the account space.
If I cleared logs, DirectAdmin would still display the account as being full, but the gameservers would run and output just fine because there was infact, real space available there. There were times where DirectAdmin would need to have a bit of a refresher to register the new space being there. By doing a search I found the solution to this. It would work, and is found here:
http://help.directadmin.com/item.php?id=39
If I increased the account size instead of clearing files, DirectAdmin would reflect the change imediately. (although I suspect it didnt update the actual space used, just the new limit)
Well now one of the accounts seems to be stuck. Inside directadmin itself, it says they are using 15.9mb / 90mb after clearing some of their logs and following the instructions at the link above. However, if I go back and do the quota -v username it still says they are over 90mb after the tally and the account isnt linked to any extra files.
I am hoping it will correct itself when DirectAdmin does its normal thing.. but this is kinda bad because his server kept refusing to run because it couldnt output any logs and I had no idea what the problem was.
I just increased it to 100, then to 120. Each time I do the quota is always the same as the limit. Also, the heading called blocks always steadily increases. Im talking like +1000 within 1 second until it reaches the same as the limit and then it has a * next to it.
[root@fracnet public_12]# quota -v snag
Disk quotas for user snag (uid 503):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 121512 122880 122880 219 0 0
[root@fracnet public_12]# quota -v snag
Disk quotas for user snag (uid 503):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 122064 122880 122880 219 0 0
[root@fracnet public_12]# quota -v snag
Disk quotas for user snag (uid 503):
Filesystem blocks quota limit grace files quota limit grace
/dev/hda3 122880* 122880 122880 219 0 0
This is the output from when I executed the quota command 3 times, in under two seconds total. Just after I increased it to 120mb from 100mb.
Any ideas? Feedback appreciated
Oh yeah, and I am using the newest DirectAdmin (updated it today after having this problem) and I am using CentOS but DirectAdmin says its Redhat. Maybe it is
-Chi
Last edited:
