Directadmin does not want to get up after update

[erick85]

The DA probably updated overnight. After rebooting, I don't want to get up. Empty error logs. What else can I do?

# /usr/local/directadmin/scripts/getLicense.sh my_license
Redirecting to /bin/systemctl restart directadmin.service
Job for directadmin.service failed because the control process exited with error code. See "systemctl status directadmin.service" and "journalctl -xe" for details.

# sh /usr/local/directadmin/scripts/getDA.sh stable
directadmin stable v1.642 f42272a9ea817a0fc6f470e3d874680cedcd36a linux_amd64: already latest

# service directadmin status
Redirecting to /bin/systemctl status directadmin.service
● directadmin.service - DirectAdmin Web Control Panel
Loaded: loaded (/etc/systemd/system/directadmin.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2022-10-04 09:08:40 CEST; 24s ago
Docs: http://www.directadmin.com
Process: 13699 ExecStart=/usr/local/directadmin/directadmin (code=exited, status=1/FAILURE)
Main PID: 13699 (code=exited, status=1/FAILURE)

Oct 04 09:08:40 myserver.com directadmin[13699]: suspend-user Suspend user
Oct 04 09:08:40 myserver.com directadmin[13699]: taskq Run dataskq
Oct 04 09:08:40 myserver.com directadmin[13699]: unsuspend-domain Unsuspend domain
Oct 04 09:08:40 myserver.com directadmin[13699]: unsuspend-user Unsuspend user
Oct 04 09:08:40 myserver.com directadmin[13699]: update Update DirectAdmin
Oct 04 09:08:40 myserver.com directadmin[13699]: version Print DirectAdmin version
Oct 04 09:08:40 myserver.com systemd[1]: directadmin.service: main process exited, code=exited, status=1/FAILURE
Oct 04 09:08:40 myserver.com systemd[1]: Failed to start DirectAdmin Web Control Panel.
Oct 04 09:08:40 myserver.com systemd[1]: Unit directadmin.service entered failed state.
Oct 04 09:08:40 myserver.com systemd[1]: directadmin.service failed.

 

[ItsOnlyMe]

Gotta love them autoupdates right..

Just try to launch it manually first by calling the binary itself and see what the error is.

/usr/local/directadmin/directadmin server

 

[erick85]

Gotta love them autoupdates right..

I ran away from cpanel (where every other morning an update crashed the server) 15 years ago to maybe a bit less functional, but painfully stable DA. And I can see that we are slowly developing in this direction...

Just try to launch it manually first by calling the binary itself and see what the error is.

Yes, I was able to run the panel like this...

 

[Richard G]

Yes, I was able to run the panel like this...

Great to hear. Maybe next time you can check the journalctl -xe too if it might happen again.
Or maybe you can check the DA logs to see if you can find some cause.

Anyway, it's odd that just starting manually fixes the issue. Hope it won't happen again.
They are improving a lot, but some things crashes with the old way, which is why for the time being I do not update DA automatically (disabled it in options.conf).

 

[fln]

Your log excerpt:

Oct 04 09:08:40 myserver.com directadmin[13699]: suspend-user Suspend user
Oct 04 09:08:40 myserver.com directadmin[13699]: taskq Run dataskq
Oct 04 09:08:40 myserver.com directadmin[13699]: unsuspend-domain Unsuspend domain
Oct 04 09:08:40 myserver.com directadmin[13699]: unsuspend-user Unsuspend user
Oct 04 09:08:40 myserver.com directadmin[13699]: update Update DirectAdmin
Oct 04 09:08:40 myserver.com directadmin[13699]: version Print DirectAdmin version

Seems like start-up scripts are trying to start DA without the `server` parameter. DA will not start without `server` parameter starting version 1.63.9. So this has nothing to do any recent updates.

For most of users migration from directadmin to directadmin server is done in update.sh:

...
DA_SYSTEMD_SERVICE=/etc/systemd/system/directadmin.service
if [ -s ${DA_SYSTEMD_SERVICE} ] && ! diff --brief ${DA_SCRIPTS}/directadmin.service ${DA_SYSTEMD_SERVICE} > /dev/null; then
    cp -f ${DA_SCRIPTS}/directadmin.service ${DA_SYSTEMD_SERVICE}
    systemctl daemon-reload
fi
...
# DA 1.63.9 use log cli arguments in init.d script
DA_INITD_SERVICE=/etc/init.d/directadmin
if [ -s ${DA_INITD_SERVICE} ] && grep -q 'PROGBIN="/usr/local/directadmin/directadmin d"' ${DA_INITD_SERVICE}; then
    sed -i 's|PROGBIN="/usr/local/directadmin/directadmin d"|PROGBIN="/usr/local/directadmin/directadmin server --daemonize"|' ${DA_INITD_SERVICE}
fi
...

If you are running OS with systemd, it could have been caused by making /etc/systemd/system/directadmin.service file immutable.

If you are running init.d based system, you might have some local modifications to the /etc/init.d/directadmin file and automatic file upgrade did not work.