On 12Dec2017 12:11, Rick Stevens <ricks@xxxxxxxxxxxxxx> wrote:
On 12/12/2017 09:09 AM, Charlie Dennett wrote:
I have a small web server and user webalizer. I recently converted to
all https. You say you "added" the ssl access log. That makes me think
you have two log files defined in your webalizer.conf file. From what I
understand, webalizer only supports one log file.
[...]
On 12Dec2017 12:11, Rick Stevens <ricks@xxxxxxxxxxxxxx> wrote:
Webalizer can only deal with a single log file at a time. You can
pass the logfile in as the last argument on the command line when
you run it (no need to bugger the webalizer.conf file or rename the
file).
Keep in mind, however, that webalizer expects data in chronological
order and if it sees a log entry from a file that is earlier than one
it has already processed, it will ignore that log entry (usually with a
message stating the fact). [...]
To get around that limitation, I wrote a program long, LONG ago that
would take logfiles from multiple servers (a load-balanced web server
cluster), interleave the entries from all of them into chronological
order and output a single file with all of the data in it. That output
file was fed to webalizer so we could analyze the cluster as though it
were a single machine. IIRC it was written in C. I can probably dig the
source code out of my archives somewhere and send it to you if you
really need it.
Me too! I used python. Mine's here:
https://bitbucket.org/cameron_simpson/css/src/tip/bin/merge-apache-logs
It could do with some polish, but we used it for years to merge apache logs
(http and https IIRC) from multiple backend servers for webalizer analysis.
Cheers,
Cameron Simpson <cs@xxxxxxxxxx> (formerly cs@xxxxxxxxxx)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
