• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved User can exceed storage limit with error_log?

destan40

Basic Pleskian
installed: centos 7.6 with quota enabled,

user can exceed storage with error_log file:
statistic shows:

Disk space: 9489%
18978.2 MB used of 200 MB

How is it possible?

cat /etc/fstab
--
proc /proc proc defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/md/0 none swap sw 0 0
/dev/md/1 /boot ext3 defaults 0 0
/dev/md/2 / ext4 usrjquota=quota.user,jqfmt=vfsv0 0 0
 
Well, you have set up Plesk to include the log files in the customer's disk space statistics (Tools & Settings -> Statistics section -> Server Statistics Settings), so that's what Plesk did.

But the actual quota on the OS level depends on the file ownership. Customer's log files are not owned by the customer's system user, but rather by root. That's why the user's actual OS level disk quota was not exceeded by having a large log file.
 
Well, you have set up Plesk to include the log files in the customer's disk space statistics (Tools & Settings -> Statistics section -> Server Statistics Settings), so that's what Plesk did.

But the actual quota on the OS level depends on the file ownership. Customer's log files are not owned by the customer's system user, but rather by root. That's why the user's actual OS level disk quota was not exceeded by having a large log file.

Yes, but if a website have a syntax error in php file for example, and this website have thousand of visitors per days,
so this error-file can break down the server if it fill up the hdd with this files...
 
Yes, but if a website have a syntax error in php file for example, and this website have thousand of visitors per days,
so this error-file can break down the server if it fill up the hdd with this files...

You could set "ignore_repeated_errors = on" in your service plans php.ini to prevent this from happening.
 
The "ignore_repeated_errors = on" directive only suppresses repeated errors from the same script, same line of the script and during the same script run. E.g., it would help if a loop within a php script would cause the same error to be repeated, but it won't help if a php script gets called by different visitors. Visitors will still cause the error to be recorded repeatedly at each visit.

The above directive combined with the "ignore_repeated_source = on" might do the trick, but I haven't dabbled in this in a long time, so please test...
 
Back
Top