Some Users/Groups Are Near Or Already Over Their Quota Limit

[unsichtbare]

I am getting emails with the message:

The following users are near or already over their quota limit on server
www.azwebdesigns.com:
================================================== =

================================================== =
================================================== =

The following groups are near or already over their quota limit on server
www.azwebdesigns.com:
================================================== =

Group: web6
Used Storage Space: 526.76 MB
Allocated Storage Space: 500.00 MB
Web Site: www.earthfriendlyfuels.net

Customer's Company: Earth Friendly Fuels
Customer's Name:
Customer's Address:
City:
Country:
Telephone:
Telefax:
Customer's Email Address:
Customer's Web Site: http://

This customer does not belong to a reseller.

but when I run du -ch I see that the customer is well within their limits at 274M.
ISPConfig also shows the customer to be within their limits, but not the same as du -ch. It shows 84M.

What is causing the erronous emails?

-J

[till]

To get the quota for a user, run:

repquota -avug

Maybe the user has files or folders in e.g. /tmp

[unsichtbare]

Thanks. Even though the site only reported using part of the allotted space, one of the mail users had used up the rest!

[till]

The admispconfig user is not able to "see" the mail files of the users, have a look here to get a better webspace usage in ISPConfig:

http://www.howtoforge.com/forums/sho...01&postcount=2

[tal56]

Was this covered in the Centos 5 perfect install? If not then I guess anyone who's done the perfect install should add this to get a better reporting of users actual statistics?

What would be the disadvantage of doing this? If there are no disadvantages, then why isnt this set by default? Thanks

[falko]

Originally Posted by tal56

Was this covered in the Centos 5 perfect install? If not then I guess anyone who's done the perfect install should add this to get a better reporting of users actual statistics?

Take a look here: http://www.howtoforge.com/ispconfig-2.x-first-steps

[tal56]

Geez, I completely missed this howto. I'm runnig through it now, looks like I've got everything setup correctly except the correct stats part, and changing the password encryption to md5.

Just curious though, if I have sites setup already, will changing the password to md5 now cause any problems? Thanks

[till]

Just curious though, if I have sites setup already, will changing the password to md5 now cause any problems?

No, Existing sites and users will not be affected.