{"id":231,"date":"2010-11-24T17:32:59","date_gmt":"2010-11-24T15:32:59","guid":{"rendered":"http:\/\/www.treg.be\/blog\/?p=231"},"modified":"2011-01-13T16:06:43","modified_gmt":"2011-01-13T14:06:43","slug":"plesk-9-x-overuse-policy","status":"publish","type":"post","link":"https:\/\/www.treg.be\/blog\/2010\/11\/plesk-9-x-overuse-policy\/","title":{"rendered":"Plesk 9.x overuse policy, server wide fix"},"content":{"rendered":"<p>Parallels implemented an overuse policy since version 9 of its Plesk control panel for Linux. When you upgrade a Linux Plesk server (8.x) to version 9.x, <strong>all<\/strong> resellers, clients an domains get the &#8220;can&#8217;t overuse&#8221; policy. So, all objects which exceed a certain value get suspended. This isn&#8217;t quite what we\/you want. (after the night, your overusing resellers\/clients\/domains will be suspended!)<\/p>\n<p>So, the solution is quite simple: just set all the objects on &#8220;allow overuse&#8221;&#8230; except that this can&#8217;t be done serverwide. If you have 300 domains + 100 clients + 5 resellers, you will have to edit 405 objects manually. \ud83d\ude41<\/p>\n<p>The solution: you can solve this problem by executing the following scripts on the Linux box from the command line (with root privileges). The script will grant clients or domains the &#8220;allow overuse&#8221; policy.<\/p>\n<ul>\n<li><strong>Clients:<br \/>\n<\/strong><\/p>\n<pre># for i in `cat \/etc\/passwd |grep \"\/var\/www\/vhosts\" | awk -F\":\" '{print $1}'`; do echo -n \"$i\u00a0 --\u00a0 \"; \/usr\/local\/psa\/bin\/client_pref --update $i -overuse notify ; echo \"\"; done<\/pre>\n<\/li>\n<\/ul>\n<ul>\n<li><strong>Domains:<br \/>\n<\/strong><\/p>\n<pre># mysql -u'admin' -p\"$(cat \/etc\/psa\/.psa.shadow)\" -D'psa' -NBe 'select name from domains order by name' | while read dom; do $(grep '^PRODUCT_ROOT_D' \/etc\/psa\/psa.conf | awk '{print $2}')\/bin\/domain_pref -u \"${dom}\" -overuse notify; done<\/pre>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Parallels implemented an overuse policy since version 9 of its Plesk control panel for Linux. When you upgrade a Linux Plesk server (8.x) to version 9.x, all resellers, clients an domains get the &#8220;can&#8217;t overuse&#8221; policy. So, all objects which exceed a certain value get suspended. This isn&#8217;t quite what we\/you want. (after the night, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[8,7],"tags":[137,114,113,112],"class_list":["post-231","post","type-post","status-publish","format-standard","hentry","category-linux","category-tech","tag-linux","tag-overuse","tag-overuse-policy","tag-plesk"],"_links":{"self":[{"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/posts\/231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/comments?post=231"}],"version-history":[{"count":10,"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/posts\/231\/revisions"}],"predecessor-version":[{"id":240,"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/posts\/231\/revisions\/240"}],"wp:attachment":[{"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/media?parent=231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/categories?post=231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.treg.be\/blog\/wp-json\/wp\/v2\/tags?post=231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}