After update DirectAdmin and reboot DirectAdmin not running

T

toktokcity

Verified User
Joined
Apr 29, 2016
Messages
96
Location
The Netherlands
Yesterday I did a reboot of a long running system and updating DA and AlmaLinux 8.1.

Afterwards the Dashboard of DA is not running. The database and webserver is running, the customers are online.

I received the following error:

● directadmin.service - DirectAdmin Web Control Panel
Loaded: loaded (/etc/systemd/system/directadmin.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2024-11-21 10:01:21 CET; 10s ago
Docs: https://docs.directadmin.com
Process: 27763 ExecStart=/usr/local/directadmin/directadmin server --syslog (code=exited, status=>
Main PID: 27763 (code=exited, status=203/EXEC)
Click to expand...

-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit directadmin.service has finished shutting down.
Nov 21 10:03:53 xxx.xx.xx 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.
Nov 21 10:03:53 xxx.xx.xx systemd[27852]: directadmin.service: Failed to execute command: Ex>
Nov 21 10:03:53 xxx.xx.xx systemd[27852]: directadmin.service: Failed at step EXEC spawning >
-- Subject: Process /usr/local/directadmin/directadmin could not be executed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The process /usr/local/directadmin/directadmin could not be executed and failed.
--
-- The error number returned by this process is 8.
Nov 21 10:03:53 xxx.xx.xx systemd[1]: directadmin.service: Main process exited, code=exited,>
Nov 21 10:03:53 xxx.xx.xx systemd[1]: directadmin.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit directadmin.service has entered the 'failed' state with result 'exit-code'.
Nov 21 10:03:53 xxx.xx.xx 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.
Click to expand...

What can I doto get this DA running again?
 
Last edited:
Did you updated your Almalinux box lately?

What you get when you run
Code: 
journalctl -xe

Check for errors

Code: 
/var/log/directadmin/error.log
/var/log/directadmin/system.log
/var/log/messages

You could update or rebuild all if needed

Code: 
da build update_full

Code: 
da build all
 
exlhost said:
Did you updated your Almalinux box lately?

What you get when you run
Code: 
journalctl -xe
Click to expand...

Yes, I did. The second quote is from journalctl -xe

/var/log/messages:
Nov 21 10:19:22 s26 systemd[1]: directadmin.service: Service RestartSec=15s expired, scheduling restart.
Nov 21 10:19:22 s26 systemd[1]: directadmin.service: Scheduled restart job, restart counter is at 2258.
Nov 21 10:19:22 s26 systemd[1]: Stopped DirectAdmin Web Control Panel.
Nov 21 10:19:22 s26 systemd[1]: Starting DirectAdmin Web Control Panel...
Nov 21 10:19:22 s26 systemd[28520]: directadmin.service: Failed to execute command: Exec format error
Nov 21 10:19:22 s26 systemd[28520]: directadmin.service: Failed at step EXEC spawning /usr/local/directadmin/directadmin: Exec format error
Nov 21 10:19:22 s26 systemd[1]: directadmin.service: Main process exited, code=exited, status=203/EXEC
Nov 21 10:19:22 s26 systemd[1]: directadmin.service: Failed with result 'exit-code'.
Nov 21 10:19:22 s26 systemd[1]: Failed to start DirectAdmin Web Control Panel.
Click to expand...
/var/log/directadmin/system.log
nothing relevant

/var/log/directadmin/error.log
empty
 
Try the update command mentioned above. and or update the box as well.

Code: 
dnf check-update
dnf update
 
No updates available. Could it be that the server started with a different AlmaLinux kernel. What will happen with the server when I am able to select a different kernel?
 
What do you see when you issue the command:
ldd /usr/local/directadmin/directadmin

Also look in your /var/log/directadmin directory for any errors in the log files located there, especially the most recent files.
 
I am on Rocky Linux 8 and this is what I see:
# ldd /usr/local/directadmin/directadmin
linux-vdso.so.1 (0x00007ffc21b82000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb74ac5a000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb74aa3a000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fb74a836000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb74a460000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb74d314000)

What OS are you on? How large is your /usr/local/directadmin/directadmin, what does it say when you do the command?:
file /usr/local/directadmin/directadmin
 
Failed to execute command: Exec format error
Click to expand...
Maybe DA didn't recognize the OS correctly on the update? Can you login to your DA account and verify the OS is still set to auto detect (or switched off). If the switch is on, check if the OS is set correctly.
 
Checked the installation with the available kernels, but DA doesn't move.

@Richard, where can I find the auto detect function in my DA account, is that something my reseller can check out?

They tried to arrange a ticket for me with the DA support, because that's not available these days anymore for simple customers like me :-(

It doesn't feel oke not being able to get access to my customers for days.
 
toktokcity said:
@Richard, where can I find the auto detect function in my DA account, is that something my reseller can check out?
Click to expand...
You have a DA license, if you got that together with a VPS or server and only the license key, then yes your vps/server provider could have a look. However in that case most likely it's in the correct state, can't hurt to have them doublecheck.

toktokcity said:
because that's not available these days anymore for simple customers like me :-(
Click to expand...
Well then they told you a lie. It's not that ticket support is not available for "simple customers", but if you have your license from your vps/server provider, then it's an internal license which also became legacy, there is no ticket support for legacy licenses.
Before they went legacy, because your vps/server provider got them major cheap, it was their job to provide support to their customers and if they could not solve it, then it was up to them to send in a ticket.
However, in those days DA even was so nice also helping those kind of customers directly via a ticket, while this is not according to the agreement.
So DA is not the bad guy here.

It's just the kind of license which does not provide ticket support except in case of a bug, but then we would see more issues with this.

toktokcity said:
Could it be that the server started with a different AlmaLinux kernel.
Click to expand...
If you updated Almalinux, for sure this is possible. It's best always to check which updates the OS is doing.
It might be possible to boot into the previous kernel again. However, that requires some delicated actions, unless your vps/server provider can do that for you or if you know how you can do that yourself.
Be aware that some things are compiled against the new kernel so you might need to compile things newly and I don't know which ones.

Maybe it's better to wait until somebody comes help here. Maybe @smtalk or @zEitEr can shed al light on this and see what can be causing this.
 
Richard G said:
Before they went legacy, because your vps/server provider got them major cheap, it was their job to provide support to their customers and if they could not solve it, then it was up to them to send in a ticket.
Click to expand...

They did send a request to DA, but their response had to do with the service level indeed. It's a pity that the level of support from a platform/operating system is not communicated during the process of building a VPS. I really enjoyed the support from DA in rarely situations in the past.
 
toktokcity said:
It's a pity that the level of support from a platform/operating system is not communicated during the process of building a VPS.
Click to expand...
Yes datacenters mostly don't do that, pity indeed. Most of them also do not inform their customers they will get a legacy license. Which is why DA created a notice on the login screen so customers get informed that way.
 
You must log in or register to reply here.
Back
Top