Directadmin not working after upgrade to Almalinux 8

K

kimbo

Verified User
Joined
Apr 23, 2013
Messages
61
Did an inplace upgrade from Centos 7 to Almalinux 8 and since then Directadmin stopped working.

Code: 
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: Starting DirectAdmin Web Control Panel...
[root@websrv01 custombuild]# journalctl -xe
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit timedatex.service has finished starting up.
--
-- The start-up result is done.
Sep 01 23:35:36 websrv01.xxx.net systemd[1]: timedatex.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit timedatex.service has successfully entered the 'dead' state.
Sep 01 23:36:36 websrv01.xxx.net systemd[1]: directadmin.service: start operation timed out. Terminating.
Sep 01 23:38:06 websrv01.xxx.net systemd[1]: directadmin.service: State 'stop-sigterm' timed out. Killing.
Sep 01 23:38:06 websrv01.xxx.net systemd[1]: directadmin.service: Killing process 80057 (directadmin) with signal SIGKILL.
Sep 01 23:38:06 websrv01.xxx.net systemd[1]: directadmin.service: Main process exited, code=killed, status=9/KILL
Sep 01 23:38:06 websrv01.xxx.net systemd[1]: directadmin.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit directadmin.service has entered the 'failed' state with result 'timeout'.
Sep 01 23:38:06 websrv01.xxx.net systemd[1]: Failed to start DirectAdmin Web Control Panel.
-- Subject: Unit directadmin.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit directadmin.service has failed.
--
-- The result is failed.
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: directadmin.service: Service RestartSec=15s expired, scheduling restart.
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: directadmin.service: Scheduled restart job, restart counter is at 12.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit directadmin.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: Stopped DirectAdmin Web Control Panel.
-- Subject: Unit directadmin.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit directadmin.service has finished shutting down.
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: Starting DirectAdmin Web Control Panel...
-- Subject: Unit directadmin.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit directadmin.service has begun starting up.
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: Starting System clock and RTC settings service...
-- Subject: Unit timedatex.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit timedatex.service has begun starting up.
Sep 01 23:38:22 websrv01.xxx.net systemd[1]: Started System clock and RTC settings service.
-- Subject: Unit timedatex.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit timedatex.service has finished starting up.
--
-- The start-up result is done.
Sep 01 23:38:52 websrv01.xxx.net systemd[1]: timedatex.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit timedatex.service has successfully entered the 'dead' state.

Code: 
 directadmin.service - DirectAdmin Web Control Panel
   Loaded: loaded (/etc/systemd/system/directadmin.service; enabled; vendor preset: disabled)
   Active: activating (start) since Sun 2024-09-01 23:38:22 CEST; 28s ago
     Docs: https://docs.directadmin.com
 Main PID: 80352 (directadmin)
    Tasks: 9 (limit: 11627)
   Memory: 9.8M
   CGroup: /system.slice/directadmin.service
           └─80352 /usr/local/directadmin/directadmin server --syslog


No idea what to do... everything is up to date. User quota settings seems to be fine. Anyone an idea? thx
 
What do you see when you do:
ldd /usr/local/directadmin/directadmin
And
/usr/local/directadmin/directadmin server --syslog

From the command line.

It’s possible that it was built with an incompatible glibc. You may need to install an RHEL8 version.
 
Did you install the needed extra software?

Try this:

Code: 
dnf install wget gcc gcc-c++ flex bison make bind bind-libs bind-utils openssl openssl-devel perl quota libaio libcom_err-devel libcurl-devel gd zlib-devel zip unzip libcap-devel cronie bzip2 cyrus-sasl-devel perl-ExtUtils-Embed autoconf automake libtool which patch mailx bzip2-devel lsof glibc-headers kernel-devel expat-devel psmisc net-tools systemd-devel libdb-devel perl-DBI perl-libwww-perl xfsprogs rsyslog logrotate crontabs file kernel-headers hostname

#and
dnf config-manager --set-enabled powertools

#and after this
da build update
da build clean
da build clean_old_webapps 
da build all

Then reboot server.
 
toml said:
What do you see when you do:
ldd /usr/local/directadmin/directadmin
And
/usr/local/directadmin/directadmin server --syslog

From the command line.

It’s possible that it was built with an incompatible glibc. You may need to install an RHEL8 version.
Click to expand...
linux-vdso.so.1 (0x00007fff7b7fa000)
libm.so.6 => /lib64/libm.so.6 (0x00007f22a5d1c000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f22a5b18000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f22a5900000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f22a56e0000)
librt.so.1 => /lib64/librt.so.1 (0x00007f22a54d8000)
libc.so.6 => /lib64/libc.so.6 (0x00007f22a5102000)
/lib64/ld-linux-x86-64.so.2 (0x00007f22a609e000)

The other command keeps on running cursor flashing and nothing happens.
 
kimbo said:
linux-vdso.so.1 (0x00007fff7b7fa000)
libm.so.6 => /lib64/libm.so.6 (0x00007f22a5d1c000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f22a5b18000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f22a5900000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f22a56e0000)
librt.so.1 => /lib64/librt.so.1 (0x00007f22a54d8000)
libc.so.6 => /lib64/libc.so.6 (0x00007f22a5102000)
/lib64/ld-linux-x86-64.so.2 (0x00007f22a609e000)

The other command keeps on running cursor flashing and nothing happens.
Click to expand...
That looks like everything "should" be working. The cursor flashing after running the "/usr/local/directadmin/directadmin server --syslog" command just means that directadmin was running in server mode and was working properly. Not sure why the service isn't starting properly. You might need to go through the steps stije listed to see if that helps.
 
toml said:
That looks like everything "should" be working. The cursor flashing after running the "/usr/local/directadmin/directadmin server --syslog" command just means that directadmin was running in server mode and was working properly. Not sure why the service isn't starting properly. You might need to go through the steps stije listed to see if that helps.
Click to expand...
The strange thing is when I run the followng: "da server --debug="2000" > /var/log/directadmin/debug.log" then DA starts working. When I close it... it stops.
 
The installation is a total mess... even the repositories were pointing to an incorrect location... have migrated from CentOS 7 to Almalinux 8... follow the guide how it should be. But it was still running on the old kernel el7 ...
 
You must log in or register to reply here.
Back
Top