We've just noticed that some of our vhosts have stopped rotating the access logs, whereas others are rotating them fine.
All of the vhosts are setup exactly the same with the default log options:
* Keep for 30 days
* Rolling size: 500M
The server-wide access log settings are:
* Keep for 30 days
* Rolling size: 10M
It seems that some of the vhost logs are using the 10M server-wide rolling size limit whereas others are using their much larger 500M vhost limit.
Our problem is that the vhosts whose logs haven't yet rotated aren't seeing any up to date webstats with awstats.
When I changed the vhost rolling size to 10M the stats have started to appear. It is strange though the inconsistent rolling log size behaviour between vhosts.
I'm using 64bit LS ent 3.3.22 with awstats 6.7
All of the vhosts are setup exactly the same with the default log options:
* Keep for 30 days
* Rolling size: 500M
The server-wide access log settings are:
* Keep for 30 days
* Rolling size: 10M
It seems that some of the vhost logs are using the 10M server-wide rolling size limit whereas others are using their much larger 500M vhost limit.
Our problem is that the vhosts whose logs haven't yet rotated aren't seeing any up to date webstats with awstats.
When I changed the vhost rolling size to 10M the stats have started to appear. It is strange though the inconsistent rolling log size behaviour between vhosts.
I'm using 64bit LS ent 3.3.22 with awstats 6.7