okay which file is it refering too? /bin/sh: line 1: 10224 File size limit exceeded/root/ispconfig/php/php /root/ispconfig/scripts/shell/logs.php >&/dev/null if i run it in a shell all i get is [root@G35 php]# /root/ispconfig/php/php /root/ispconfig/scripts/shell/logs.php File size limit exceeded my website statistics are not updating because of this on any of my sites.
Hi, this seems to be a general problem with PHP. PHP seems not to be able to append data to files > 2 GB. I've found this workaround, but I did had the time to test it yet: http://de.php.net/manual/en/function.fopen.php#37791 Another solution will be to hack the logs.php script, that it rotates the logs on a daily basis instead of a monthly rotation.
Daily work great for me, i dont know what will happend when i get a daily log bigger than 2Gb.. but they are all around 700Mb so, no problem for a while..
i found it, one of the log files for the month of july in our main site was 2.1 gigs. i deleted it and the stats updated for all the sites.
Yep, one web.log file bigger than 2Gb and webalizer will not run. Please, put a daily web.log by default.
I put this on our todo list Anyone with a bit spare time wants to make a patch for the webalizer.php script ?
So what should that patch exactly do? Just rotate the file after calling the webalizer? Or did you mean logs.php, because if I see that right, webalizer.php does not really read that logfile...
You are right, I meant the logs.php file. Instaed of rotating the logfile monthly, it can be rotated daily. I guess the script part in webalizer.php that removes logfiles when the max. logfile space has exceeded will have to be changed too.
You ve sent it to me, works great on my servers: http://www.howtoforge.com/forums/showthread.php?t=5763
what about a simple fix of making a cron to move the file everyday after stats run and place it in a new folder? or what about just deleting it? i use awstats more then webalizer since it is not a commercial hosting server and for one private party.
