Updating DA Version Endless Loop

beansbaxter

Verified User
Joined
Mar 17, 2004
Messages
218
Location
WA
The current DA update seems to be in an endless loop.

I did the usual update to DA to the most recent version. I was alerted with a notification in the Licensing/Update section, and saw there was a new menu variable for DA version preference. Since is a production server with clients, I chose the "Stable-Delayed release schedule" and DA proceeded to restart.

Now in the CustomBuild section, the DA version is 1.63.0 and it wants to update to 1.62.4... ok, so I revert back and then it does it again the opposite direction and wants to upgrade to 1.63, and keeps repeating.

Seems like an endless loop...
 
files9 is a 3rd party mirror, see;


Try setting the downloadserver option manually first to files1, then disable 3rd party mirrors in options.conf (don't know the option out of my head), then do

Code:
./build update
./build set_fastest

This way you are using one of the official mirrors and this will probably solve your issue.

You probably want to do ./build versions also because files9 seems to be very out of date.
 
I followed the above steps. I didn't see the third party option in there, but changed it to files1.directadmin.com

The build set_fastest decided to change it to files.directadmin.com

In the DA control panel, I noticed the Licensing/Update section no longer allowed me to choose the DA release type.

From there, I went ahead and updated DA:

Screen Shot 2021-10-22 at 11.10.45 PM.png

And of course, DA had to restart...

Waited 10 minutes and DA is not responsive. Server and websites are running fine, but I cannot access DA control panel anymore. I tried restarting DA from the command line, and got the errors below:

Code:
[root@server custombuild]# service directadmin restart
Redirecting to /bin/systemctl restart directadmin.service
Job for directadmin.service failed because a fatal signal was delivered to the control process. See "systemctl status directadmin.service" and "journalctl -xe" for details.
[root@server custombuild]# systemctl status directadmin.service
● directadmin.service - DirectAdmin Web Control Panel
   Loaded: loaded (/etc/systemd/system/directadmin.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Fri 2021-10-22 16:14:58 UTC; 12s ago
     Docs: http://www.directadmin.com
  Process: 3410 ExecStart=/usr/local/directadmin/directadmin d (code=killed, signal=SEGV)
 Main PID: 20243 (code=killed, signal=KILL)

Starting DirectAdmin W...
directadmin.service: c...
Failed to start Direct...
Unit directadmin.servi...
directadmin.service fa...
Hint: Some lines were ellipsized, use -l to show in full.
[root@server custombuild]#
 
And the results now from journalctl -xe

Code:
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit directadmin.service has begun starting up.
systemd[1]: directadmin.service: control process exited, code=killed s
systemd[1]: Failed to start DirectAdmin Web Control Panel.
-- Subject: Unit directadmin.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit directadmin.service has failed.
--
-- The result is failed.
systemd[1]: Unit directadmin.service entered failed state.
systemd[1]: directadmin.service failed.
polkitd[567]: Unregistered Authentication Agent for unix-process:3891:
systemd[1]: Started Session 171418 of user root.
-- Subject: Unit session-171418.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-171418.scope has finished starting up.
--
-- The start-up result is done.
CROND[3914]: (root) CMD (/usr/local/directadmin/dataskq)
 
Back
Top