Projects / Webalizer


The Webalizer is a Web server log analysis program. It is designed to scan web server log files in various formats and produce usage statistics in HTML format for viewing through a browser.


Recent releases

  •  16 Mar 2012 08:14

    Release Notes: This release adds full IPv6 support, extended history capabilities, support for bzip2 compressed files (in addition to the existing gzip compression support), native geolocation services as well as the ability to use the GeoIP database, expanded DNS capabilities, large file support (>2GB), additional output control, many new configuration keywords/features, a modest speed improvement, and more.

    •  24 Jul 2008 11:28

      Release Notes: Enhanced history display, improved DNS capabilities, native geolocation (fully supporting both IPv4 and IPv6 lookups), additional output functionality, and much more.

      •  18 Apr 2002 20:34

        Release Notes: This is a bugfix release, with additional support for extended characters, fixes for blank hostnames (yes, they have been found), a fix for a buffer overflow in the DNS code, a fix for a KByte total mismatch, and updates for several language files.

        •  03 Nov 2001 19:03

          No changes have been submitted for this release.

          •  17 Oct 2000 11:03

            Release Notes: Bugfixes.

            Recent comments

            04 Apr 2006 10:54 bugmenot

            Error: Unable to restore run data (8)
            Recently, my Webalizer froze and did not display any data after a specific day. It gave the following error:

            Error: Unable to restore run data (8)

            and something about a dns-cache.db lock.

            To resolve this, I did the following:

            Erased all my httpd log files (/etc/httpd/access_log).

            Erased the old non-updating webalizer output pages at (var/www/html/usage) which varies by install.

            Erased everything in (/var/lib/webalizer) which included:





            I then restarted webalizer by typing 'webalizer' at the SSH command prompt using PuTTy.

            Although this erased all my logs and prior info, it got things running again. Next time, I'll try deleting the HTTPD log files last to see if it works.

            Good Luck!

            17 Jan 2006 10:05 brouits

            Re: Version 2.01.11
            Did you commit your polish translation to the awffull ( webalizer fork ? it could be nice.

            > I've released un-official version
            > 2.01.11.

            17 Jan 2006 09:59 brouits

            Re: User Color configurable
            This patch is now maintained an have a webalizer-usercolor ( freshmeat entry.

            > I wrote a patch for webalizer that allow
            > one to customize the colors of the
            > charts with his/her own 10 colors map,
            > in webalizer.conf.

            09 Feb 2005 23:45 chongo

            webalizer-2.01-10 patch for your consideration
            We have been successfully using modified webalizer-2.01-10 extensively on multiple sites, from the very large to the very small for some time now.

            We have made a number of mods to the standard webalizer-2.01-10 distribution as well as built a number of tools to process multiple virtual sites as well as to create summary/rollup stats for all of the virtual sites on a given server.

            The topic of this posting are the patches that we have applied to the webalizer-2.01-10 distribution. The URL:


            contains 4 patches, 3 of which I recommend to all webalizer users and the 4th is a re-package of the geolizer patch.

            The 0.basic.patch:


            does the following:

            * ability to process very large log files (> 2GB in size)
            * countries patch

            Some of the entries on the list are not countries. In some cases the nation state status is contested. In other cases the entry is related to a territory that does not claim to be a country. In some cases what some claim is a country is in dispute by another country. And things like .arpa are not a country.

            I recommend that one use the term 'location' instead of
            'Nation' or 'Country' to avoid the whole mess. ;-)

            Added are some missing locations (from the ISO UN codes and from GeoIP's list). Some location names have been corrected or changed to their official name. Added some more TLDs.

            * avoid referrer spamming (IMPORTANT)
            Spammers and other low-life forms have been stuffing the "top N referrer" table in order to get webalizer to generate links to their sites ... (perhaps because they think this will improve their search engine placement or perhaps because they wish to direct people to a poisoned web page in an effort to exploit some browser bug?). Whatever the reason, we don't need to give them their links.

            This patch turns the "top N referrer" table into just values instead of A tag.

            * correctly process log entries made during a leap second
            * long referrer and search patch

            Quite a few referrer and search strings are between 128 and 256 chars in length. Avoid truncating them.

            The 1.64bit.patch:


            does the following:

            * avoid 32 bit counter overflow

            For very busy sites, 32 bit signed counters can overflow. This is particularly when using webalizer to cover a long span of time. This patch converts a few values to be u_int64_t to avoid these numeric overflow problems.

            The 2.hist.patch:


            does the following:

            * extend the summary page for longer than 12 months

            By default, webalizer only keeps the last 12 months of data. And at the start of a month, the oldest month is discarded resulting in only 11+ months of data.

            This code gets around the 12 month limit by maintaining a history of older months in a parallel directory ../history.

            See the webalizer page:


            for an example of this effect.

            NOTE: After the 2.hist.patch has been applied, the
            track-hist tool:


            should be run on a monthly basis. See the comments in the 2.hist.patch file as well as the track-hist tool itself for details.

            The optional 3.geolizer.patch patch:


            is If AND ONLY IF you use one the MaxMind
            ( GeoIP database. It is a just a reapplication of the geolizer.patch that works for Un*x / Linux / GNU-Linux systems after the first 3 patches have been applied.

            -=-=- in Summary -=-=-

            At a minimum, I'd highly recommend the 0.basic.patch patch.

            Large web sites will want the 1.64bit.patch patch (after the 0.basic.patch has been applied). It doesn't hurt smaller sites to have it either.

            Sites that want to keep more than 12 months of webalizer stats need the 0.basic.patch, 1.64bit.patch and the 2.hist.patch as well as the track_hist tool.

            chongo (Landon Curt Noll) /\oo/\
            Share and enjoy! :-)

            23 Oct 2004 03:39 wfmh

            Version 2.01.11
            Since Webalizer author seems not to be interested in further development, I'd like to inform anyone insterested, that I've released un-official version 2.01.11. CHANGELOG ( and archives can be found there: ;)


            Project Spotlight


            A Fluent OpenStack client API for Java.


            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.