#1  
Old 26th July 2010, 11:09
abubin abubin is offline
Member
 
Join Date: Mar 2010
Posts: 81
Thanks: 0
Thanked 2 Times in 2 Posts
Default apache log issues

My website is only serving around 10 websites.

One of the website is very active thus generating lots of logs.

I just found out about this only when I got alerted for diskspace running out email.

I tried searching in ispconfig and there are no option to disable logging for certain website.

I am using ispconfig 3.0.1.6.

Can I know where I can disable http logging for specified websites?? I think this is a pretty important feature and I assume it is already implemented? Maybe I didn't find properly?

What about compressions on the logs? Is there any?

What about log rotate?

As of now, these 3 features seems like not available. Without these, the logs will build up like crazy, even for a normal website, the logs generated daily is around 1GB already. With compression, this could reduce to 100mb.

Please help....thanks.
Reply With Quote
Sponsored Links
  #2  
Old 26th July 2010, 11:18
abubin abubin is offline
Member
 
Join Date: Mar 2010
Posts: 81
Thanks: 0
Thanked 2 Times in 2 Posts
Default

Just manage to view back one of the thread about compression of log.

http://www.howtoforge.com/forums/sho...light=compress

I looked at my cron_daily.php file and there are lines already added for compression of logs and also removal of logs more than 30 days. But seems like this is not running properly. Don't know why...anyone can take a look into this?
Reply With Quote
  #3  
Old 26th July 2010, 11:32
abubin abubin is offline
Member
 
Join Date: Mar 2010
Posts: 81
Thanks: 0
Thanked 2 Times in 2 Posts
Default

When I rung the cron_daily.php manually,

I get error: Warning: Truncating oversized referrer field

This could be the thing causing the failed access_log files processing?
Reply With Quote
  #4  
Old 26th July 2010, 12:24
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,703
Thanks: 819
Thanked 5,320 Times in 4,173 Posts
Default

Quote:
This could be the thing causing the failed access_log files processing?
No. The truncate error is normal and happens on log lines that are too long.

Please update your server to ispconfig 3.0.2.2 as it has an improved log handling.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #5  
Old 28th July 2010, 08:18
abubin abubin is offline
Member
 
Join Date: Mar 2010
Posts: 81
Thanks: 0
Thanked 2 Times in 2 Posts
Default

i have upgrade to 3.0.2.2. There are no additional function for handling logs per website. I am assuming the improved log handling you meant was the compression and 30 days removal script is working now?

If not, please do point me to the right direction.

Thanks.
Reply With Quote
  #6  
Old 28th July 2010, 12:11
abubin abubin is offline
Member
 
Join Date: Mar 2010
Posts: 81
Thanks: 0
Thanked 2 Times in 2 Posts
Default

i have looked at another server that is using 3.0.2.1. The logs compression is there for most of the domains except for 2. One is as11 and as11.domain.com. FYI, as11 is the server's hostname. So it's like the compression doesn't work on local hostname.

Upgrade to 3.0.2.2?
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Apache Log File + Webalizer - Bytes Transferred mooxe Server Operation 0 24th January 2010 22:57
FTP Problems wabz Installation/Configuration 6 11th January 2010 18:51
Issues reloading apache config Norman General 5 2nd March 2009 12:14
CENTOS 5 Ping Problem gAnDo Server Operation 11 28th March 2008 20:58
Centos 4.4 32bit Hangs, High Server load 3cwired_com Server Operation 11 16th November 2006 15:47


All times are GMT +2. The time now is 20:11.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.