I had the same problem as mentioned above....
I only noticed after the logs.php script started spitting out 'File Size Exceeds Limit'. I figured out that the web.log of one of my sites had hit the max 2gb filesystem limit. I cleared it, ran the logs.php again and got the readlink error for localhost. To get around it I created the site localhost in ispconfig, and also created a symlink to that localhost dir. I had to make the symlink because ispconfig would only create a symlink for www.localhost
. Once I did this, the logs.php went through without a problem (got rid of the warning readlink error).
One of my sites does around 9,000,000 pages per month... the logs average over 200MB per day. Does any of the scripts cull the logs in /var/log/httpd? Or should I be doing this manually? How soon after the current day can I remove the ispconfig access file?