Unable to find the webalizer binary (solved)

[Freddy]

My webalizer statistics don't update. The DirectAdmin Task Queue Log tells me the following:

2022:10:13-00:10:42: Unable to find the webalizer binary: /usr/bin/webalizer. Download a new binary: http://files.directadmin.com/services/

Which is a little weird since this is a newly installed server. It is running Debian 11 (Bullseye).

Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 5.10.0-18-amd64
Architecture: x86-64

I installed DirectAdmin on a fresh Debian installation with this command:

bash <(curl -fsSL https://download.directadmin.com/setup.sh) 'Provided license key should go here'

I tried fixing webalizer by (re)installing it through the custombuild command:

/usr/local/directadmin/custombuild/build update
/usr/local/directadmin/custombuild/build webalizer

This gave the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether ln -s works... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether char is unsigned... no
checking for u_int64_t... yes
checking whether altzone is declared... no
checking for main in -l44bsd... no
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking for main in -lm... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking for main in -lz... yes
checking for gzrewind in -lz... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for main in -lpng... yes
checking for main in -lgd... no
configure: error: gd library not found.. please install libgd
Trying to make webalizer...
make: *** No targets specified and no makefile found. Stop.

Looks like i'm missing a library. So how to install libgd in the correct way so that DirectAdmin can use it?

 

[Freddy]

I see that there is a libgd-dev package in Debian. But this is a development version. Is there also a non-development version? Like a stable production version?

And does Webalizer work with this libgd-dev version?

 

[Freddy]

I took a gamble and installed libgd-dev on a server with few clients. After that Webalizer installed good.
Added a tally task to Task.queue and the stats seem to be generating like they should.

Problem solved.

 

[Ohm J]

it already fix in DA1.64.4

 

[Freddy]

it already fix win DA1.64.4

"Already" after several months. I found the same problem on a server I installed 5 months ago. Didn't notice it because those clients never used Webalizer.

 

[Ohm J]

it new version update.

Version 1.644 | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

 

[Richard G]

"Already" after several months. I found the same problem on a server I installed 5 months ago.

If nobody reports, and nobody discovers, it won't be fixed. And then things can take longer. Bind had a bug for many years.

 

[Freddy]

If nobody reports, and nobody discovers, it won't be fixed. And then things can take longer. Bind had a bug for many years.

I perfectly understand. My reaction was just because jamgames2 said it "already" had been fixed. It sounded like this bug was just introduced in the last version and the fix was here before anyone noticed it.

I didn't report this bug by the way so its a total coincidence that I'm just posting this topic while it has been officially fixed. I searched this whole forum and found no recent posts about this bug.