Recompile the Webalizer against the new version of gd..

--

On Mon, 17 May 2010, Sara Pipe wrote:

> Dear Ger,
>
> I also upgraded gd again. But no luck. I have gd-2.0.35 and it is giving the
same error.
>
> :(
>
> --- On Mon, 5/17/10, Sara Pipe <sara_im_pipes@...> wrote:
>
> From: Sara Pipe <sara_im_pipes@...>
> Subject: Re: [webalizer] webalizer hangs on "History file not found..." 
message
> To: webalizer@yahoogroups.com
> Date: Monday, May 17, 2010, 9:17 AM
>
>
>
>
>
>
>
>  
>
>
>
>
>
>
>
>
>
>      Hi Ger,
>
> Thanks for your reply.
>
> Do you know which version of gd do I have to install? I have  webalizer-2.
21-02 and libpng-1.2.18.
>
> Thank you,
> Sara
>
> --- On Mon, 5/17/10, Ger Hobbelt <ger@hobbelt. com> wrote:
>
> From: Ger Hobbelt <ger@hobbelt. com>
> Subject: Re: [webalizer] webalizer hangs on "History file not found..." 
message
> To: webalizer@yahoogrou ps.com
> Date: Monday, May 17, 2010, 8:44 AM
>
>
>
>
>
>
>
>  
>
>
>
>
>
>
>      From the error message, I'd say it looks like webalizer directly or
indirectly uses libgd as well (haven';t checked, this is off the cuff) and libgd
is complaining. Given that you reported a webalizer source install, the way
forward would be to check if libgd is required (most probably, as gd is often
used for graphing) and when yes, gd must also be upgraded, alas.
>
>
>
> --
> Met vriendelijke groeten / Best regards,
>
> Ger Hobbelt
>
> ------------ --------- --------- --------- --------- --
> web:    http://www.hobbelt. com/
>        http://www.hebbut. net/
>
> mail:   ger@hobbelt. com
> mobile: +31-6-11 120 978
> ------------ --------- --------- --------- --------- --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

I have webalizer 2.01 on Centos with virtual hosts,
many thanks for this tool.

Noticing as there is a 2.2 version, I d/l and installed 2.2

it all seems fine, the 2.2 installed into /usr/local/bin

is there anything I should do with 2.2 ?

I also d/l GeoDB and flags

do I just move flag images to \icons\ where the other images live ?

I copied GeoDB to
# webalizer -vV
Webalizer V2.21-02 (Linux 2.6.9-55.0.9.EL i686) English
Copyright 1997-2009 by Bradford L. Barrett
Mod date: 13-Jan-2009  Options: DNS/GeoDB
Default GeoDB dir : /usr/share/GeoDB
Default config dir: /usr/local/etc

# ls /usr/share/GeoDB
GeoDB.dat  GEODB.README

is that of use to me, or, is logresolve enough ?


webalizer is called from a script like:

...
logresolve < /home/$i/logs/$DATE-access.log > /home/$i/logs/$DATE-access.rog
...
/usr/local/bin/webalizer -n $i -o /home/$i/www/stats/webalizer
/home/$i/logs/$DATE-access


thanks


--
Voytek

It's basically a drop in replacement.. if you just upgrade, it will continue to
function as it did before and default to the same settings.  If you want to use
the GeoDB database, add the '-j' switch to your script.  If you want to use
country flags, the default location for them is in the 'flags' directory under
whatever directory you are generating output in.. to use them, you must add the
'CountryFlags yes' directive in your configuration file.  If you want to locate
the images someplace other than the default, you can specify where they are with
the 'FlagDir' directive.  See the supplied documentation (README, man page,
sample config file) for additional information.

--

--- In webalizer@yahoogroups.com, "Voytek Eymont" <voytek@...> wrote:
>
> I have webalizer 2.01 on Centos with virtual hosts,
> many thanks for this tool.
>
> Noticing as there is a 2.2 version, I d/l and installed 2.2
>
> it all seems fine, the 2.2 installed into /usr/local/bin
>
> is there anything I should do with 2.2 ?
>
> I also d/l GeoDB and flags
>
> do I just move flag images to \icons\ where the other images live ?
>
> I copied GeoDB to
> # webalizer -vV
> Webalizer V2.21-02 (Linux 2.6.9-55.0.9.EL i686) English
> Copyright 1997-2009 by Bradford L. Barrett
> Mod date: 13-Jan-2009  Options: DNS/GeoDB
> Default GeoDB dir : /usr/share/GeoDB
> Default config dir: /usr/local/etc
>
> # ls /usr/share/GeoDB
> GeoDB.dat  GEODB.README
>
> is that of use to me, or, is logresolve enough ?
>
>
> webalizer is called from a script like:
>
> ...
> logresolve < /home/$i/logs/$DATE-access.log > /home/$i/logs/$DATE-access.rog
> ...
> /usr/local/bin/webalizer -n $i -o /home/$i/www/stats/webalizer
> /home/$i/logs/$DATE-access
>
>
> thanks
>
>
> --
> Voytek
>

<quote who="thewebalizer">

> It's basically a drop in replacement.. if you just upgrade, it will
> continue to function as it did before and default to the same settings.
> If you want to use the GeoDB database, add the '-j' switch to your
> script.  If you want to use country flags, the default location for them
> is in the 'flags' directory under whatever directory you are generating
> output in.. to use them, you must add the 'CountryFlags yes' directive in
> your configuration file.  If you want to locate the images someplace
> other than the default, you can specify where they are with the 'FlagDir'
> directive.  See the supplied documentation (README, man page, sample
> config file) for additional information.

thanks,

all's well
I overlooked that as installed 2.2 was looking at /usr/local/etc for
webalizer.conf. (and, I put correct path for flags, but, forgot to remove
'#' from the line...)



--
Voytek

what is the proper way to exclude or ignore 'service pages' such as
'/webmail' and '/stats' ?




--
Voytek

now that I've installed 2.2, I wanted to reprocess some old logs, I get like:

...
16 records (16 ignored) in 1 seconds, 16/sec
89 records (89 ignored) in 1 seconds, 89/sec
105 records (105 ignored) in 1 seconds, 105/sec

do I just delete webalizer.hist 1st, before reprocessing ?


--
Voytek

Hello,

I would like to know if there is any place where Webalizer is logging its
**own** actions, or if there is any mean to have it logging them ?

I sometime have to find debugging problems with Webalizer, and I always spend a
lot of time in doing that, because if for example Webalizer doesn't work because
it is handling a corrupted file, it just stops working without giving any error
message, and it is very difficult to find the reason of the problem.

I looked also about using the "-d" or "-v" options, but these are command line
options which are very hard to add when the actual call to Webalizer is actually
deeply buried inside a Perl script not written by yourself.

Best regards,

Gingko

I recently had to reconfigure my Apache set up, but am at a loss to explain why
I am getting this error in Webalizer:

Jim-Coyles-iMac:~ jimcoyle$ webalizer
Webalizer V2.01-10 (Darwin 10.4.0) English
Error: Can't open log file /private/var/log/httpd/access_log

Is this some sort of new permissions error or????

On 8/24/2010 20:15, James Coyle wrote:
> I recently had to reconfigure my Apache set up, but am at a loss to explain
why I am getting this error in Webalizer:
>
> Jim-Coyles-iMac:~ jimcoyle$ webalizer
> Webalizer V2.01-10 (Darwin 10.4.0) English
> Error: Can't open log file /private/var/log/httpd/access_log
>
> Is this some sort of new permissions error or????

i don't know about "new" but it seems like it might be... what are the
permissions on that directory and log file and what are the user and group that
webalizer is running as??

I can't get dumps to run - everything else is working great - but dumps refuse
to be generated. Here is my .conf:

OutputDir      /var/www/html/rep-stats
Incremental yes

PageType htm*
PageType cgi
PageType php

CountryGraph no
IndexMonths 24
GraphMonths 24

TopSites        0
TopKSites       0
TopURLs         1500
TopKURLs        20
TopReferrers    0
#TopAgents       0
TopCountries    0
TopEntry        0
TopExit         0
TopSearch       0
#TopUsers        20
AllURLs        yes

HideURL  *.gif
HideURL  *.GIF
HideURL  *.jpg
HideURL  *.JPG
HideURL  *.png
HideURL  *.PNG
HideURL  *.ra
HideURL  *.css
HideURL  *.js
HideURL         /image/*

MangleAgents    1

DumpHeader yes
DumpExtension csv
DumpURLs yes

Any ideas?  This system is running Fedora and Apache.

Hi

The current groupdomains paramaters works like

GroupDomains 1

would group

alpha.site.org.uk
beta.site.org.uk
gamma.this.org.uk
delta.this.org.uk
eta.other.com
theta.other.com

into two groups

org.uk
and
other.com

I would really like to be able to group by actual domain name i.e with
out the short hostname. i.e. into groups

site.org.uk
this.org.uk
other.com

I reliase it can be done for explicit domain names that I mention but I see no
way of doing it genrally.

Essentially it would be

GroupDomains -1

Is there a way to achieve this?

Steve.

Hi,

I have a weird problem that I don't understand. I added a HTMLTail option in
webalizer.conf file and when I generate it, I obtain this link twice in the
webpage at the right bottom.

Do you know if it's a knowned bug in Webalizer ?

This is the code I added:

# HTMLTail defines the HTML code to insert at the bottom of each
# HTML document, usually to include a link back to your home page.
HTMLTail <a href="index.html" target="_self">Return to site</a>

NOTE: I run Webalizer on Debian 4.1.2 in the cron.daily job with the default
options set.

In the past (many years ago) I used Red Hat 7.3 and I never see this problem.

Sounds like you are having your config file read twice.. are you
doing something like "-c webalizer.conf" on the command line when
you run the program?

If so, don't :)   See the webalizer FAQ (question #11)

--

On Sun, 26 Jun 2011, glenn_gagne wrote:

> Hi,
>
> I have a weird problem that I don't understand. I added a HTMLTail
> option in webalizer.conf file and when I generate it, I obtain this
> link twice in the webpage at the right bottom.
>
> Do you know if it's a knowned bug in Webalizer ?
>
> This is the code I added:
>
> # HTMLTail defines the HTML code to insert at the bottom of each
> # HTML document, usually to include a link back to your home page.
> HTMLTail <a href="index.html" target="_self">Return to site</a>
>
>
>
>
> ------------------------------------
>
> Webalizer homepage: http://www.webalizer.org
> Yahoo! Groups Links
>
>
>

You're right !

I analyzed the /etc/cron.daily/webalizer file and it call something like:
webalizer -c all_conf_files_in_webalizer_folder -Q

Then I modified the script file to call simply webalizer -Q and it work fine !!!

Thank you

--------------

P.S. Weird that default Debian setting decided to call the default
webalizer.conf file and scan all conf files in /etc/webalizer folder too.



This problem is solved for me now !

Hello,

i need to create some statistics for the past 6 Months.
I have a bunch of apache accesslogs which are namen like
access_log-20110110, access_log-20110111 and so on.

How can I geht webalizer to process all these files and create stats for the
months?

I tried different configfile where each has one logfile in it,
but it created onyl the august stats.
than I try to run on commandlince with the -p option and i also only got august.

than I joined all my logfiles with the logfilemerger from the readme, but i
still only got august.

I already spent hours on this.
What is the proper way to analyse multiple logfiles?


thnx

I'm running into an issue with Webalizer after upgrading to Gallery3. It seems
Gallery3 places index.php in between the domain and the directory structure of
the website.  For example, www.domain.com/index.php/2011/summervaction/

As a result, Webalizer is stripping the "index." and everything after. This
makes the stats read as if every single request is for /

I see in the configuration file where I can add additional IndexAlias
definitions but there doesn't appear to be away to exclude "index."  Does anyone
know if this is possible?

Thanks in advance for any suggestions!

Dallas

Try using:

DefaultIndex  no


in your config file..

Here is the relevant bit from the README file:

DefaultIndex  This option is used to enable/disable the use of "index." as
                a default index name to be stripped from the end of a URL.
                Most sites should not need to use this option, however some
                may find it useful, particularly those whose default index
                file name is something different, or those sites that use
                'index.php' or similar URLs to generate dynamic content.
                This option does not effect any of the names that may be
                defined using the IndexAlias option, and those names will
                still function as described.  Values may be 'yes' or 'no',
                with 'yes' being the default.

--

On Mon, 15 Aug 2011, tankman67 wrote:

> I'm running into an issue with Webalizer after upgrading to Gallery3.
> It seems Gallery3 places index.php in between the domain and the
> directory structure of the website.  For example,
> www.domain.com/index.php/2011/summervaction/
>
> As a result, Webalizer is stripping the "index." and everything after.
> This makes the stats read as if every single request is for /
>
> I see in the configuration file where I can add additional IndexAlias
> definitions but there doesn't appear to be away to exclude "index."
> Does anyone know if this is possible?
>

--
Bradford L. Barrett                      brad@...
A free electron in a sea of neutrons     DoD#1750 KD4NAW

The only thing Micro$oft has done for society, is make people
believe that computers are inherently unreliable.

Thanks for the reply Bradford.  I'll provide a little more detail.  I installed
Webalizer with apt-get on my Debian system.  This installed version 2.01.  I
checked the README located in /usr/share/doc/webalizer and did some Googling -
which I try to do to prevent asking stupid questions - but didn't see this
option.

I took your advice however, but received the following output:
Warning: Invalid keyword 'DefaultIndex' (/etc/webalizer/webalizer.conf)

I see the README file at ftp://ftp.mrunix.net/pub/webalizer/README (which
appears to be for version 2.23-05) DOES contain this option.

I will try upgrading my Webalizer version and test.  Thanks again for pointing
me in the right direction here.

Dallas

--- In webalizer@yahoogroups.com, "Bradford L. Barrett" <brad@...> wrote:
>
>
> Try using:
>
> DefaultIndex  no
>
>
> in your config file..
>
> Here is the relevant bit from the README file:
>
> DefaultIndex  This option is used to enable/disable the use of "index." as
>                a default index name to be stripped from the end of a URL.
>                Most sites should not need to use this option, however some
>                may find it useful, particularly those whose default index
>                file name is something different, or those sites that use
>                'index.php' or similar URLs to generate dynamic content.
>                This option does not effect any of the names that may be
>                defined using the IndexAlias option, and those names will
>                still function as described.  Values may be 'yes' or 'no',
>                with 'yes' being the default.
>
> --
>
> On Mon, 15 Aug 2011, tankman67 wrote:
>
> > I'm running into an issue with Webalizer after upgrading to Gallery3.
> > It seems Gallery3 places index.php in between the domain and the
> > directory structure of the website.  For example,
> > www.domain.com/index.php/2011/summervaction/
> >
> > As a result, Webalizer is stripping the "index." and everything after.
> > This makes the stats read as if every single request is for /
> >
> > I see in the configuration file where I can add additional IndexAlias
> > definitions but there doesn't appear to be away to exclude "index."
> > Does anyone know if this is possible?
> >
>
> --
> Bradford L. Barrett                      brad@...
> A free electron in a sea of neutrons     DoD#1750 KD4NAW
>
> The only thing Micro$oft has done for society, is make people
> believe that computers are inherently unreliable.
>

All Website access statistics, whether produced by Webalizer or some other
package, suffer from at least one important limitation - they don't distinguish
between access requests from humans and those from Web crawlers (good or bad). 
That's not a problem if you're just looking at capacity management issues, but
it's a huge problem if you want to learn about which parts of your Website are
valuable to your human visitors.

I think I've figured out a way to overcome that limitation (mostly), so I'm
writing to y'all to lay out my ideas, report progress, and ask for comments. 
And the process of writing this will help to clarify what I'm thinking.

The raw data contains no explicit indication of what caused each access attempt,
but it does contain clues from which useful information can be deduced.  After
looking at raw data several different ways, I've come up with what I hope is a
useful approach, based on agent-id.

The basic approach is to use those clues to make a best guess as to which agents
are used by humans and which are bots.  Then use that distinction to split each
access log into two or three parts (human, bot, and maybe indeterminate). 
Finally, use Webalizer to re-analyze whichever part(s) I/we find interesting.

So what are the clues?

1.  Anything that requests "favicon.ico" is most probably a browser used by a
human, while anything that requests "robots.txt" is almost certainly a bot.  A
tiny number of agents ask for both, and a large number ask for neither, so those
are indeterminate at this point.  I've written an analysis program, which
provided the following figures from our first full month of operation:
- nearly 93000 access requests
- from just over 1700 agents
- of which 540 occurred only once
- leaving 1170 reasonably analyzable
- of which over 700 requested favicon.ico
- - - and over 100 requested robots.txt
- - - (though 10 requested both)
- - - leaving over 300 requesting neither

2.  An agent which is only seen once in a month is most probably a bot,
especially if its ID looks like a random string of characters.  (See above for
counts.)

3.  Some access requests identify a referrer [typically misspelled "referer" in
server documentation], but most do not.  It seems likely that those which do
probably come from humans, but this clue requires further investigation.  At the
moment all I can say is that our first month's data shows that about 30% of
requests come from referrals, and about 2/3 of those are from our own Website.

4.  Successful requests for items contained in a password-protected directory
must come from humans.

5.  Requests for items which were never on our Website (e.g., PHP files - YMMV)
must indicate hacker intrusion attempts, which probably would be carried out by
robots.

Further programming is required to investigate these clues more deeply and to
make use of the results.  Meanwhile ...

Questions?  Comments?  Suggestions?

(and does anyone have a Webalizer binary for Mac OS X - any version?)

Carl Scott Zimmerman

Hi,
I joined to see if anyone can help me with a strange problem.
I'm sysadmin at a hosting and web marketing company. Several of our customers
have had their sites moved from one server to a new one to upgrade. The
webalizer stats show some marked differences in data reported between the two,
most notably the Pages and Visits results, which have been reduced by up to 75%.
The config and data have been checked and are identical between the two servers,
so what can it be doing differently?
Can anyone help please?

Thanks very much.
Sam Gyseman.

All:

I have a CentOS 5.2 box running my website, using webalizer to track stats. I am
provisioning a new CentOS 6 box to house the site. Migration of the website,
database, etc. is pretty straight forward. I am a little nervous about moving
webalizer logs over. Has anyone done this before? Any tips you can offer to
insure a smooth transition (and preservation of log data)?

The CentOS 5 box is running webalizer v. 2.01-10
The CentOS 6 box is running webalizer v. 2.21-02

Thanks in advance.
Rich Lohman