![]() |
Logsize issue
Last week I set the logsize on a site to 5MB, still today the web.log file is 24MB. Any way to fix this or am I just not understanding logsize and how it works?
|
Please check your sysleog if you have any cron errors. The logfile size is checked by the script /root/ispconfig/scripts/shell/webalizer.php
|
There are no errors. The cron log shows the webalizer.php running as it should.
|
I have no other Idea. I added this thread to the bugtracker, maybe there is something wrong with the webalizer.php script. But as far as I can see, it works on my servers.
|
Logsize is a problem
I am seeing a problem with web.log size too.
These are the logs located in /var/www/web2/log/2007/11 /var/www/web2/log/2007/12 My November web.log is 3.8GB My December log is already 1.5GB I have logsize set to 5 in ISP Manager but it doesn't seem to matter. There are no errors in the cron log to indicate a problem with webalizer: Code:
|
I have 2 ISPConfig servers. One is CentOS 5.1 32-bit the other is 64-bit.
Both of them have this logsize problem with web.log. Is there a patch to fix this? |
We'll check that - I've added it to our bugtracker.
|
This has become a huge issue for us. I just had to delete a 31 GB error.log which brought a site down. Is there anything else that can be done?
|
This is a problem!
Quote:
I'm having to monitor log size and manually delete them when they get over 5 GB. My logs are bigger than my webs! |
We haven't had the time yet to check this, but be assured that we will. :)
|
| All times are GMT +2. The time now is 06:02. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.