DA won't start after updating to v1.669

[krisiskris]

So yesterday I updated DA on one of our servers from 1.668 to 1.669. Since then, we're not able to start DA at all.
Running da from the commandline results in:

Segmentation fault (core dumped)

This also means any da related commands to try and rebuild or update, won't work either.
Looking into /var/log/directadmin/error.log doesn't reveal anything relevant.

We tried debugging the application, but I'm not sure what to make of the output:

(gdb) run server --debug=2000
Starting program: /usr/bin/da server --debug=2000
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__memchr_evex () at ../sysdeps/x86_64/multiarch/memchr-evex.S:324
324 VPCMP $0, (%rdi), %YMMMATCH, %k1

Running a backtrack gives slightly more info, but I'm still uncertain what to make of it.

(gdb) bt
#0 __memchr_evex () at ../sysdeps/x86_64/multiarch/memchr-evex.S:324
#1 0x00007ffff72f312e in two_way_short_needle (needle_len=10, needle=0x7ffff7ff1411 "usage: ssh", haystack_len=<optimized out>, haystack=0x4002ed "ux-x86-64.so.2") at str-two-way.h:303
#2 __GI___memmem (needle_len=10, needle_start=<optimized out>, haystack_len=<optimized out>, haystack_start=<optimized out>) at memmem.c:73
#3 __GI___memmem (haystack_start=<optimized out>, haystack_len=<optimized out>, needle_start=0x7ffff7ff1411, needle_len=10) at memmem.c:43
#4 0x00007ffff7fedaef in ?? ()
#5 0x000000000000fd00 in ?? ()
#6 0x00007ffff7dd80e2 in _dl_map_segments (loader=<optimized out>, has_holes=<optimized out>, maplength=<optimized out>, nloadcmds=<optimized out>, loadcmds=<optimized out>, type=<optimized out>, header=0x7ffff7ffe238, fd=<optimized out>, l=0x0) at ./dl-map-segments.h:141
#7 _dl_map_object_from_fd (name=<optimized out>, origname=<optimized out>, fd=<optimized out>, fbp=0x7ffff7ffe230, realname=<optimized out>, loader=<optimized out>, l_type=<optimized out>, mode=<optimized out>, stack_endp=<optimized out>, nsid=<optimized out>) at dl-load.c:1181
#8 0x0000000000000000 in ?? ()

Interestingly enough, all the sites on the server seem to be working fine. Also sending and receiving e-mails is working fine as far as I can see (tested with Roundcube to external addresses)

I ran this info through ChatGPT which is advising me to reinstall DA entirely, but I'm a bit reluctant to do that, as I don't want to lose all my configs and data.

Do you guys have any advice on that to do in this situation?

Edit: please note, there's loads of RAM available, It's not a memory related issue!


Thanks,
Kris

 

[LawsHosting]

Maybe the wrong OS in the license?

 

[krisiskris]

Maybe the wrong OS in the license?

How do I check or correct this? This Direct Admin server has been running for a long time in its current state.

 

[LawsHosting]

In your DA client area on this site.... or, if you bought it from a reseller, their client area.

 

[fln]

@krisiskris, please open a support ticket at https://tickets.directadmin.com. Seems strange, but if we can get access to the machine we will find the root cause.