Plesk 9.x overuse policy (and how to avoid domains being suspended)

Parallels, in their infinite wisdom, introduced new “overuse” policies into their Plesk control panel as of version 9.0.  A great idea when just starting out, but a nightmare when upgrading from a previous version, since it changes the default behavior when clients and domain owners reach their pre-assigned limits.  Now, instead of just warning that you’re over a limit, it SUSPENDS the account and domain. What a great idea, how useful!  Clients *love* that!

So how do you undo this when you have new accounts being added, and existing accounts that don’t allow for this type of “overuse” setup, and are suspending clients and domains when they use 1KB more disk space or 1KB more bandwidth than they are supposed to?

New accounts can take advantage of the new “overuse policy” settings within the templates, but existing clients are going to have a tougher time, you’ll have to update their policy in a template, then apply the new template, or you can use the CLI utilities and change the overuse policy per client, which is what I opted for here.

Using the Plesk CLI utilities (here running on CentOS 5.x):

replace “clientuser” with your client login name you wish to update

check client preferences for their overuse policy:

/usr/local/psa/bin/client_pref.sh –info clientuser |grep Overuse

Overuse policy:                block

  • For checking all clients on the system (produces a lot of random output):

for i in `cat /etc/passwd |grep “/var/www/vhosts” | awk -F”:” ‘{print $1}’`; do echo -n “$i  —  “; /usr/local/psa/bin/client_pref –info $i |grep Overuse; echo “”; done

update overuse policy to “notify” rather than “block”:

/usr/local/psa/bin/client_pref.sh –update clientuser -overuse notify

  • updating all your clients at once:

for i in `cat /etc/passwd |grep “/var/www/vhosts” | awk -F”:” ‘{print $1}’`; do echo -n “$i  —  “; /usr/local/psa/bin/client_pref –update $i -overuse notify ; echo “”; done

check if it was updated:

/usr/local/psa/bin/client_pref.sh –info clientuser |grep overuse

Overuse policy:                notify

No longer need to worry about client accounts and domains being suspended due to being over their limits by mere kb!  Will need to keep an eye on their use though, and watch overuse emails, since this does mean users could abuse the “limits” that have been set for them now.

Now on to the domains!

Once you’re done with fixing up the client accounts, you will have to double check all those domains if you don’t want them being suspended.

The following is for editing ALL domains on the Plesk system,  you can just run the domain_pref script on a single domain at a time if you prefer.

check domain preferences for their overuse policy:

for i in `ls -1 /var/named/run-root/var/ | egrep -v ‘(in-addr.arpa|localhost.rev|saved_by_psa|named.root|make-localhost)’`; do echo -n “$i : “; /usr/local/psa/bin/domain_pref –info $i |grep Overuse; done

update overuse policy to “notify” rather than “block” on all domains:

for i in `ls -1 /var/named/run-root/var/ | egrep -v ‘(in-addr.arpa|localhost.rev|saved_by_psa|named.root|make-localhost)’`; do echo -n “$i : “; /usr/local/psa/bin/domain_pref –update $i -overuse notify ; done

Background:

Fairly unresolved discussion of this issue here: http://forum.parallels.com/showthread.php?t=85216

From the Plesk documentation

Overuse policy. Specify what should be done to the site when disk space and traffic limits are exceeded: To block the site, select the Overuse is not allowed option. To allow the site to operate, select the Overuse is allowed option. Select the check box Notify the domain owner about reaching the resource limits: When the specified resource usage limits are reached, Parallels Plesk Panel will send a notice to the appropriate client account’s e-mail address (by default) or to the domain administrator’s account, if that is specified at Home > Notifications (in the Logs & Statistics group) > Resource usage limits exceeded by domain option.Note: The overuse policy does not apply to the limits set on size of mailboxes (mailbox quota). Therefore, even if you enable overuse, be sure to allocate enough disk space to mailboxes.

From the administrators guide:

Overuse policy. Specify what should be done when disk space and monthly bandwidth (traffic) allotments are exceeded. We recommend setting this option to Overuse is allowed. Otherwise, the user account and user’s sites will be blocked when the resource limits are exceeded.

2 comments

  1. Thanks for this article. It saved me from having to manually update these settings on thousands of domains and clients across several servers on a Saturday afternoon. Now I have time to go out and rake the leaves….YAY!

Leave a Reply

Your email address will not be published. Required fields are marked *

*