Fix Webalizer for making it solve countries/domains

I have done so, we will have to wait until tomorrow, to see the results.

BTW Is this the only way to fix it?
Isn't it suppossed that webalizer have a hostname lookup logic included?
(Just like awstats does)

I am affraid that this apache tweak may affect its performance....

UltimeWWW said:
In your httpd.conf, put "ON" to HostnameLookup.

Thanks.
Click to expand...
 
If apache doesn't do the hostname lookup, the logs would not contain the required information by webalizer to show those stats, I think.
So webalizer does have the capability, but theres no information to parse unless that apache is loggin that kind of stuff.
Which can technically require a little more resources.
 
Originally posted by jmstacey If apache doesn't do the hostname lookup, the logs would not contain the required information by webalizer to show those stats, I think. So webalizer does have the capability, but theres no information to parse unless that apache is loggin that kind of stuff. Which can technically require a little more resources.
Click to expand...

That is tough for me to understand.

Since I have been with DA there have been many different threads about making the countries work. God knows how many hrs of time have been wasted on this minor issue by untold numbers of us? I know I have wasted lots of time and took me 6-mos to finally get it working!

Why not simply either have it set to work upon installation or during the install process ask if we want countries to work, yes or no? Very simple.

All these threads and posts about this are insanity. I really am at a loss to understand why DA can not deal with such a simple issue like this (and other issues to)?
 
Last edited:
DA is supposed to (and does) do only the base installation. That is all (and should be) required of it. Any other modifications that you would prefer should be the responsibility of the server administrator.

Having the installation program ask for every single detail on what you want would be unrealistic in my opinion. It would also make installation very inneficient and non-automated, with the requirment of an admin to be answering its questions.

I hope you are exagerating on the 6 months bit as it should not have taken more than a day at the extreme most in my opinion unless there is something terribly wrong with your installation. Since there is documentation.


quote:Originally posted by jmstacey If apache doesn't do the hostname lookup, the logs would not contain the required information by webalizer to show those stats, I think. So webalizer does have the capability, but theres no information to parse unless that apache is loggin that kind of stuff. Which can technically require a little more resources.



That is tough for me to understand.
Click to expand...

Webalizer only parses what is in the apache log files. If hostname/country infromation is not in the apache log files, then there is nothing that webalizer can show. That is why you must enable apache to collect that information and add it to the logs.
 
I wonder if it would be safe to recompile webalizer-

I have seen that there is a enable-dns
option for compiling webalizer, that is supposed to do what I need.

Needless to mention the GeoIP plugin that would also provide an enhanced nslookup functionality..

jmstacey said:
DA is supposed to (and does) do only the base installation. That is all (and should be) required of it. Any other modifications that you would prefer should be the responsibility of the server administrator.

Having the installation program ask for every single detail on what you want would be unrealistic in my opinion. It would also make installation very inneficient and non-automated, with the requirment of an admin to be answering its questions.

I hope you are exagerating on the 6 months bit as it should not have taken more than a day at the extreme most in my opinion unless there is something terribly wrong with your installation. Since there is documentation.




Webalizer only parses what is in the apache log files. If hostname/country infromation is not in the apache log files, then there is nothing that webalizer can show. That is why you must enable apache to collect that information and add it to the logs.
Click to expand...
 
jmstacey said:
DA is supposed to (and does) do only the base installation. That is all (and should be) required of it. Any other modifications that you would prefer should be the responsibility of the server administrator.
Click to expand...

But why in the world make it a needed modification? Why would anyone want the country display disabled, I am positive the vast majority want it to display the countries? Why not simply enable it upon base installation, and perhaps make disabling it a modification? That would seem to make much more sense.

Regarding it taking so long to get it working, yet it is so but of course I did not work on the issue every day but did from time to time over 6 mos. I recall seeing many other posts about it being a lengthy job to figure the modification out so not just me. Thanks for your reply.
 
Last edited:
According to
/usr/local/directadmin/customapache/build file

webalizer is compiled without the --enabledns option
therefore, that is the reason why my attemps for enabling dns lookup never work...

I have tried to recompile webalizer manually with the enable dns option, but I got an error message that says that I have a Berkeley DB library missing, so that's another story to work in.

But I guess that I am near to the solution than 1 day ago :cool:
 
This is what I have in

/usr/local/directadmin/data/templates/custom/webalizer.conf


Code: 
DNSCache /var/lib/webalizer/dns_cache.db
DNSChildren 10

and it works.
 
Webalizer and dns again

I have noticed that the newest recompilation scripts for webalizer
include the --enable-dns command.

How can I see the recompilation
process and its results for debugging?

I recently found this document that states that I need two extra rpms
for having the dns feature working.
http://webalizer.org/faq.html (item 18, db1 and the db1-devel RPMs)

However after installing these rpms in my Redhat box, this thing still doesn´t work.
db1-1.85-8.i386.rpm
db1-devel-1.85-8.i386.rpm
 
You must log in or register to reply here.
Back
Top