awstats
 

Hey, quick and simple question.

How do i put the logfile parameter option so i can read from 2 or 3 servers that are being load balanced by a Cisco CSS? The shitty manual just says cluster support and that's it, and the example in the conf file just says '.../logresolvemerge.pl *.log |'. This tells me nothing.

For instance, let's say i got web servers 10.0.0.5 and 10.0.0.6, how do i put that parameter there?

Thanks in advanced.

I don't have a way to try what i'm saying but I believe logresolve only sorts records on the fly to be analyzed from several log files at the same time. So what you shoul provide in the config is

path_to_log_resolve/logresolvemerge.pl file1_in_10.0.0.5.log file2_in_10.0.0.6.log ... >finallog.log

and then tell awstats to analize that finallog.log

like i said haven't try it cause I have no servers using clustering.

Ou, ok, thanks man. And once again my point is proven. The shitty manual just doesn't specify if it does that on the fly or if you have to throw the resulting merged file into another one, and then have the config file specify that final log for awstats to analize. Anyways, i'll sort it out with more googling and hopefully anybody will throw me a bone here. Appreciate your help man, cool. :study:

keep me posted if that works for you. thanks.

This piece of ...
 

Another thing, i sorted some other problems here. But now, apparently, awstats does not like having * characters when specifying the logfile parameter. Or maybe i am doing something else wrong. And yeah man, i'll keep you posted. It's kinda of intriguing trying to find out things by yourself, knowing that the manual is worth nothing. Jejejeje. :scratch:

yes, awstats does not support wildcards in logfile parameter. instead of this, when you want to specify mutliple log files you should use following syntax:

LogFile="..bla-bla/logresolvemerge.pl logfile1 logfile2 logfile3 | "

in your case, when you want to analyse log files from multiple servers at one place, i think it will be simplier to write a script which will do the following:
1. sync all log files to pc where awstats analysis will perform. you can do it with rsync for example...
2. if you like the idea, you can merge you log files in one huge - ..bla-bla/logresolvemerge.pl logfile1 logfile2 logfile3 > huge-log-file.log
3. run awstats analysis.

Mighty helpfull info friend!!! I'll be sure to check all this at once. I'll post back to this same reply with the updates of my findings. You seem to know your stuff man, cool and thanks a lot. :study:

i've completed configuring awstast for my sites recently , that is why i'm able to advice you something.

good luck :)

Maybe you two can get together and mail awstats with an example, it's a pain in the tail trying to find out all this on your own.

maybe we should think about it :)

You guys are probably going to kill me.

I installed awstats for windows, on another server. Made a script to merge all log files for each site into one, and have this one file fed to the awstats perl command.

It's working nice now. I wish i could have done that with linux. :cry:

and what is your problem on Linux? as i know awstats is natively created for Linux, so on Win you should expect more problems. And if you done it on Windows you will do it on Linux too :)

:scratch: It's quite simple: the server that runs linux, the server running the company's internal DNS, is having some problems, and the main thing is that named service stops resolving, so my boss, which is not linux savy, decided to move that to windows. So, since i haven't been to fix it yet, i am screwed, now i got no more linux machines to fix.

That's the reason why i installed awstats on windows. Pretty shitty situation, and i feel pretty bad cause i don't know exactly how to fix this problem, mainly because i don't know where to start looking. Linux is a bit complicated for me still, and i've been using it for a bit more than 2 years now, and it still puzzles me on a daily basis.

Any whoooo.... i hope one day i can become one of you guys, linux savys, that would rock.

Thanks for the help.

Hey, i am back here for a problem i am having with awstats. As i stated here in the previous messages, i installed awstats on windows. Not anymore, i got it up and running on my linux box for testing. Well, turns out that the information displayed by awstats is completely wrong. Here's an output of what it shows when performing the analysis:
Note the extremely large amount of corrupted records. Amazingly, i followed the exact instructions in making the log files in IIS suitable for awstats to analyze. You know, you gotta select some fields in specific (date time c−ip cs−username cs−method cs−uri−stem
cs−uri−querysc−status sc−bytes cs−version cs(User−Agent) cs(Referer)sc−status sc−bytes cs−version cs(User−Agent) cs(Referer)) according to the official pdf manual.

I first noticed that there was something wrong because for instance, i got 2300 hits for only 4 visitors. That is just not right. And after that, i installed two other log file analyzers, and they showed very similar results; results that made a lot of more sense and showed a lot more information.

Thanks in advanced for the help guys.

I would suggest check very carefuly that the log your log files and the log awstats expects to analize is the same, check the config file and the log files, they should match, you should also check your logs to see the hits, because there are some errors that awstats read as corrupted but you can tell it not to.