Webalizer not able to show IP locations
- Thread starter logixsols
- Start date
enable reverse IP lookups in webalizer.conf
Richard G
Verified User
Is that still up to date? If yes, then it's incomplete, it states:
But this directory does not even exists so needs to be created first in that case.
But this directory does not even exists so needs to be created first in that case.
As this documentations says none of the things match. It old or useless documentation.
This also not worked.
None of the thing or solution matches.
Please suggest any other solution.
Richard G
Verified User
As I said, you have to create the directory /var/lib/webalizer as it does not exist.
You clearly did not do that first, hence the error notice you display in the last screenshot.
So first create the /var/lib/webalizer directory and after that use the chmod command.
[root@server lib]# mkdir webalizer
[root@server lib]# chown root:root /var/lib/webalizer
[root@server lib]# chmod 1777 /var/lib/webalizer
[root@server lib]#
[root@server lib]#
I've create a directory and then apply these permissions and still IP locations not showing.
[root@server lib]# chown root:root /var/lib/webalizer
[root@server lib]# chmod 1777 /var/lib/webalizer
[root@server lib]#
[root@server lib]#
I've create a directory and then apply these permissions and still IP locations not showing.
zEitEr
Super Moderator
From "/etc/webalizer.conf.sample":
Code:
# The GeoIP option enables or disables the use of geolocation
# services provided by the GeoIP library (http://www.maxmind.com),
# if available. Values may be 'yes' or 'no, with 'no' being the
# default. Note: if GeoDB is enabled, then this option will have
# no effect (GeoDB will be used regardless of this setting).
#GeoIP noFrom https://docs.directadmin.com/direct...html#how-to-customize-the-output-of-webalizer
DirectAdmin uses the default webalizer settings by not specifying a webalizer.conf file at all. If you want to adjust the settings for webalizer, you can create your own basic webalizer.conf file for DA to use. This file must be domain-independent because this one file will be used for all domains without any modifications to it.
zEitEr
Super Moderator
No. Read the directadmin guide page on how to customize Webalizer and make it to use webalizer.conf, or hire somebody to do it for you.
Ahahahaha
Means your documentation is not correct. If a developer unable to understand it.
Second, I tried the same documentation dozens of times but it not worked.
I used it on lot of servers, It worked perfectly.
Here I not know, Why you make binaries of all things and then change a configuration and re-compile the things.
Honestly, You try to enable these settings on your side and share the screenshot to me.
I hope you also can't do it.
Last edited:
zEitEr
Super Moderator
Good to see you laughing. I don't work for DirectAdmin and don't write documentations for their site. But I found information on how to use custom webalizer.conf there.
I don't know why it does not work on your side and have no guide for your case either. I don't use Webalizer for my own needs, and if you want me to investigate and fix your issue, you will be charged hourly rate. Of course if I have time to do it for you.
@zEitEr Thanks for your time.
Any official developer here ?
@DirectAdmin Sales @DirectAdmin Support @fln @karolis @scriptkitty @smtalk
Any official developer here ?
@DirectAdmin Sales @DirectAdmin Support @fln @karolis @scriptkitty @smtalk
zEitEr
Super Moderator
@Richard G, thank you for tagging me here. I believe webalizer is abandonware, and no longer being developed. A GeoDB.dat file required for the software is missing on a server and no longer downloadable from the official site of the software. Webalizer does not like modern GeoIP.dat and GeoLite2-Country.mmdb files from geoip and geolite packages:
Code:
BDB0210 /usr/share/GeoDB/GeoDB.dat: metadata page checksum error
Code:
BDB0641 __db_meta_setup: /usr/share/GeoDB/GeoDB.dat: unexpected file type or formatSo if you have webalizer working on any old server, you might try and copy the file GeoDB.dat to the new server and see whether or not it helps. Or it should be re-compiled with --with-geoip support.
Probably DirectAdmin developers can help more.
zEitEr
Super Moderator
Richard, I completed a custom installation of Webalizer with enabled GeoIP support and it worked on my end. DirectAdmin does not support a custom configure.webalizer file, so it was a manual installation from a source file. Since that countries are detected fine.
You might request directadmin developers to add GeoIP support in Webalizer. I still prefer Awstats
Thank you so much.
Means I was right the documentation is not updated / Not up-to mark for developers.
Second, Custom Installation works that's not an issue.
But Again in DirectAdmin it not works.
Custom is just 3 commands
sudo apt install webalizer
sudo nano /etc/webalizer/webalizer.conf
LogFile /usr/local/lsws/logs/access.log (Point to your log file)
OutputDir /home/<my_domain>/public_html/stats
HostName <my_domain>
GeoIP yes
GeoIPDatabase /usr/share/GeoIP/GeoIP.dat
and run it
/usr/bin/webalizer -Q
Then go to <my_domain>/stats
Again my question is, Its not working in DirectAdmin.
Then what documentation says us ?
Richard G
Verified User
Thank you. I was just trying to help the TS and couldn't, so I thought maybe you had some insight or idea and indeed you do. Thank you for your responses in this thread.
And for bringing this to our attention. Seems we can better remove Webalizer totally from the servers, which I personally already did on most of them.
I personally wasn't intending to use it, just trying to help. But thank you for the explanation and the test you did.
But imho it might be better indeed to not work with non supported/updated software anymore. And Awstats is working fine indeed.