Is there any issue tracking traffic after the access log passes 1GB in size?

AnkitG

Registered
Sep 24, 2006
2
0
151
I have a client who has a website that was getting thousands of visitors per day, but is now reporting to get a number under 500. This client was getting somewhere in the 5 digit range for about a week because of some links that were put around, and so a drop was expected, however not such a large one.

I've checked with both awstats and webalizer and they report similar results.

Is there any known issue for something like this? The access log is past 1GB in size and it's possible that could be the issue. Also, when we use the "update now" link at the top of the page, it doesn't change anything like it did in the past. It only seems to work at night.

How exactly does the OS handle the file? One possibility is that if during the day the large 1GB file is being opened/closed repeatadely, then that could be why it isn't updating almost in real time as it should if you click the link. It does work for other clients on the server though.

Any thoughts on this would be appreciated.
 

AnkitG

Registered
Sep 24, 2006
2
0
151
No, it is still updating at night on a regular basis however not during the day when the user clients on the update now link.
 

jay711

Member
May 2, 2005
6
0
151
did you fix the problem? i have the same issue. Apache stops logging to access log after the file is a bit larger than 1GB.
 

freedman

Well-Known Member
Feb 13, 2005
312
1
168
I noticed that my domlogs stopped getting updated at 1GB.

after issuing an httpd restart
the logs are updating and, I presume, will go up to 2gb where the unix filesize limitation will hit.

I think the reason I hadn't noticed a problem before was that the logrotate was restarting httpd often enough that it was resetting apaches log file pointer???

anyway, it's a stop gap.
/etc/logrotate.d/httpd
is run weekly, so if apache needs to be restarted more often a cron or /etc/cron.daily or some other solution will apply to your invidual situations.