Systemd SEGV

M

mamorunl

Verified User
Joined
Jun 4, 2019
Messages
10
Hi all,

We are still having some ubuntu 16 servers running, waiting to be upgraded to ubuntu 18 and 20. Ubuntu 16 runs on debian 9, but we had to specify debian 8 in the license to have it running on older binaries - which was the instruction given by DirectAdmin itself.

Since an update in may/june this year, after a reboot of the server, systemd crashes with a segfault. I thought it was a broken server at first, but now we had to restart all servers and the problem arises with almost all servers with this configuration.

The only thing we have found to have stopped systemd from crashing right away, is to stop directadmin from launching. All other processes run fine until we start directadmin again. The segfault comes back almost instantly. Also, if directadmin fails to start on boot, the whole server stops booting further.

Does anyone know why this is? I'd rather not spend all evenings reinstalling servers and putting back backups from servers with 600G disks :D
 
Just a small update on this end:

I have found out that if I do /usr/local/directadmin/directadmin o, it points out that it was compiled for CentOS. I have added Debian+8+64 in the /root/.os_override file and downloaded everything for debian 8, but the error remains.

The full error is:

Code: 
Jul 19 19:46:50 da02 kernel: [  275.473595] systemd[1]: segfault at 0 ip           (null) sp 00007ffce46c0238 error 14 in systemd[55f45ead6000+160000]
Jul 19 19:46:50 da02 systemd[1]: Caught <SEGV>, dumped core as pid 4318.
Jul 19 19:46:50 da02 systemd[1]: Freezing execution.
 
ben29 said:
it's look for me like old workaround.
try use the new binary.
Click to expand...

I have tried both Debian 9 and Debian 8 files, but it all ends up in a segfault:

Code: 
Broadcast message from systemd-journald@servername-omitted (Mon 2021-07-19 22:12:36 CEST):

systemd[1]: Caught <SEGV>, dumped core as pid 3683.
 
After I turned on the debug mode of grub, I got the following error messages:

Code: 
Jul 19 23:47:40 vm02 systemd[1]: Got message type=method_call sender=:1.2 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/session_2d44_2escope interface=org.freedesktop.DBus.Properties member=Get cookie=43 reply_cookie=0 error=n/a
Jul 19 23:47:40 vm02 systemd[1]: session-44.scope: Failed to load configuration: No such file or directory
Jul 19 23:47:40 vm02 systemd[1]: Sent message type=method_return sender=n/a destination=:1.2 object=n/a interface=n/a member=n/a cookie=1987 reply_cookie=43 error=n/a
Jul 19 23:47:40 vm02 systemd[1]: session-44.scope: Collecting.
Jul 19 23:47:40 vm02 systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=UnitNew cookie=1988 reply_cookie=0 error=n/a
Jul 19 23:47:40 vm02 systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=1989 reply_cookie=0 error=n/a
Jul 19 23:47:40 vm02 systemd[1]: Received SIGCHLD from PID 4396 (sudo).
Jul 19 23:47:40 vm02 systemd[1]: Child 4396 (sudo) died (code=exited, status=1/FAILURE)
Jul 19 23:47:40 vm02 systemd[1]: user-1000.slice: Child 4396 belongs to user-1000.slice

After the above, the message from the last post comes on.
 
You must log in or register to reply here.
Back
Top