Starting emhttpd via command line results in segfault

Hi folks,

I've got a remote server that I administer and I have a script running on a raspberry pi at the same location which logs into the server using ssh every 5 mins and copies the array encryption keyfile over (if not already there) and starts the array (if not already started). This is a bit convoluted but it's been working fine. The remote location has quite a lot of power cuts hence the janky setup. The pi holds the keyfile on a ramdisk and fetches it from a different remote server on boot.

For the last several weeks I don't seem to be able to start the array via the script, it just hangs at "starting services".

This is the command in the script to start the array:

ssh -i $ssh_key root@$server_adress 'emcmd cmdStart=Start'

And this is the only weird thing I can see in the syslogs:

Dec 17 16:30:04 TOWER kernel: emhttpd[9208]: segfault at 0 ip 000014d7971cc9c7 sp 000014d796a1ce78 error 4 in libc-2.37.so[14d79708a000+169000] likely on CPU 5 (core 6, socket 0)
Dec 17 16:30:04 TOWER kernel: Code: 48 01 d0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 c4 41 01 ef ff 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 29 03 00 00 <c5> fe 6f 07 c5 fd 74 0e c5 >

The array starts aboslutely fine if I port forward to the web interface via the raspberry pi and start it using the gui.

The server is very minimal with a simple array and 3 docker images.

Any ideas?

Cheers!

Edited December 17, 20241 yr by Doggeh