Webalizer doesn't work, error with 'libgd.so.2'

Aar

Verified User
Joined
Feb 10, 2005
Messages
209
Location
Netherlands
Hello,

I've figured out that Webalizer doesn't working on my server. I see the error:
webalizer: error while loading shared libraries: libgd.so.2: cannot open shared object file: No such file or directory

I've tried to follow the steps from this outdated article:
https://help.directadmin.com/item.php?id=56
But it still doesn't works! I dont have the file: libgd.so.2 in the directories /usr/local/lib/libgd.so.2 and /usr/lib/libgd.so.2

I'm un-sure about the command, and i haven't run this yet:
Code:
yum install gd
gd library is still working and compiled in PHP. Is it safe to run this command?
And you can either AW-stats like Webalizer run simultaneously?
 
Last edited:
I have contacted John, and he says this:

Maybe rename your current webalizer, and try this one: http://files.directadmin.com/services/es_6.0_64/webalizer to see if it works for you.
If not, back to CentOS 7 64: http://files.directadmin.com/services/es_7.0_64/webalizer
Both binairies doesn't work. The '6.0_64' version gives:
error while loading shared libraries: libdb-4.7.so: cannot open shared object file: No such file or directory

What is wisdom and the best practice??
1) Use the 'es_7.0_64' version and install gd library (from custombuild? or by yum?)
2) Use the '6.0_64' version and install the db-library with yum install libdb-devel or yum install libdb libdb-dev
3) Or else ...?
 
I have tried: yum install gd gd-devel

It give me this error: Error: libX11 conflicts with libxcb-1.9-5.el7.x86_64

And a lot of lines after this: ** Found 85 pre-existing rpmdb problem(s), 'yum check' output follows: etc....

What now?
And what if i set webalizer to 0 in directadmin.conf?
I have an idea that the tally doesn't works because webalizer isn't working

Any idea????
 
How did i get these rpm-problems?

Can i solve it with this?
Code:
yum clean all 
rpm --rebuilddb
yum update
 
the commands won't break anything and they worth trying...
...according to my experience you won't fix the issue with them. It's most likely that you have conflicts on packages versions installed from different unofficial repos.
 
Back
Top