Plesk Error Log Too Big
Contents |
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base
Parallels Log File
Documentation Downloads Plesk University Release notes Blog Become a Partner Russian parallels.log file huge German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian plesk 12 log rotation any Search error_log occupied too much space and was not rotated Article ID: 118799, created on Nov 21, 2013, last review on Jun 23, 2016 Applies
Plesk Log Rotation
to: Plesk 12.5 for Linux Plesk 12.0 for Linux Plesk 11.0 for Linux Plesk 11.5 for Linux Plesk 10.4 for Linux/Unix Symptoms Log rotation for a domain is setup to rotate logs by size, but error_log file occupies too much space and not being rotated upon reaching the configured size. Cause Log rotation
Parallels Support
is performed by the Daily Maintenance script. This task will rotate a log file in case if its size is equal or larger than configured. So if the size of log file exceeds a particular limit, but the Daily Maintenance is not started yet then log file will not be rotated (until Daily Maintenance has started). Resolution Configure a cron task to rotate logs for affected domain individually: Editing crontab: crontab -e Create a crontask with similar content: 01 01,05,10,15,20 * * * /usr/local/psa/logrotate/sbin/logrotate /usr/local/psa/etc/logrotate.d/example.com -s /usr/local/psa/var/logrotate.status After that log rotation will be performed 5 times a day for the domain 'example.com'. Search Words Logrotation does not work properly not rotated . disk usage logs are not rotated log rotation 1 log rotation by size does not work a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 742559b1631652fadd74764ae8be475e e335d9adf7edffca6a8af8039031a4c7 2a5151f57629129e26ff206d171fbb5f Email subscription for changes to this article RSS subscription for changes to this article Save
for UNIX/Linux where log files for a specific virtual host took up a larger than normal amount of space. In Parallels Plesk 11 you can actually modifying log file settings through the Control Panel GUI. The below are examples of some of the log files in Parallels Plesk 11 which grew large in size, approximately 200 MB each which chewed through hosting space. /var/www/vhosts/
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://stackoverflow.com/questions/2832743/access-log-is-huge-not-being-archived-how-to-reset-it the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each log file other. Join them; it only takes a minute: Sign up access_log is huge, not being archived. how to reset it? up vote 5 down vote favorite 3 I have discovered that my access_log is occupying most of my HDD. It's over 200 GB in size. How can I reset it ? I am using Apache 2.2.3 on a CentOS plesk error log server with Plesk. Thank you guys ! apache access-log share|improve this question asked May 14 '10 at 8:21 user290367 31114 add a comment| 7 Answers 7 active oldest votes up vote 12 down vote knx'answer is good, but I would suggest to rename the log, and create a new one, so that you can restart apache without waiting for the access log to be compressed, which can take a while if it's big. needs access to ssh First, rename the current log file: mv /var/log/apache/access.log /var/log/apache/access.log.1 Second, create a new log file and give the same permissions, owner/group and selinux context as the original one: touch /var/log/apache/access.log chown --reference=/var/log/apache/access.log.1 /var/log/apache/access.log chmod --reference=/var/log/apache/access.log.1 /var/log/apache/access.log restorecon --reference=/var/log/apache/access.log.1 /var/log/apache/access.log (probably need to be root to do that) Next, restart apache Then Gzip the old file (text files compression ratios are really good). If we assume the file is named /var/log/apache/access.log then do this: gzip -c /var/log/apache/access.log.1 > /var/log/apache/access.log.1.gz these 4 points are what logrotate do automatically. share|improve this answer edited May 7 '11 at 13:46 Stu