• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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