2.3.1 Segmentation Fault Error on startup

[mcoutsoft]

Installed 2.3.1 yesterday and noticed twice today while changing aquilink.conf and re-starting that I am hitting segmentation fault errors on startup.

Thought it may be the power supply, so I swapped that out and a couple of hours later, got another segmentation fault on startup.

Reinstalled 2.3.1 and it went away, but came back again.

Swapped the SDCard for a different card, re-imaged and a few restarts later, I turned on log to disk and am getting a segmentation fault again.

Reinstalled 2.3.1 (using command line below) and things are back to normal.

curl -s https://raw.githubusercontent.com/sfeakes/AqualinkD/master/extras/aqua.sh -o aqua.sh && chmod 755 aqua.sh && ./aqua.sh release
Local AqualinkD version 2.3.1 is latest, not downloading
Installing AqualinkD
Please enabled cron.d support, if not AqualinkD Scheduler will not work
Edit /etc/default/cron and look for the -l option, usually in EXTRA_OPTS
AqualinkD config exists, did not copy new config, you may need to edit existing! /etc/aqualinkd.conf
AqualinkD defaults exists, did not copy new defaults to /etc/default/aqualinkd
Avahi/mDNS defaults exists, did not copy new defaults to /etc/avahi/services//aqualinkd.service
AqualinkD web config exists, did not copy new config, you may need to edit existing /var/www/aqualinkd//config.js
Starting daemon aqualinkd
Installed Aqualink Daemon 2.3.1
No arguments supplied, please use use:-
./aqua.sh release <- Download & install latest AqualinkD stable release.
./aqua.sh latest <- Download & install latest AqualinkD version. (development release)
./aqua.sh force_latest <- Force latest option (don't run any version checks)
./aqua.sh install <- Install to local filesystem, (config files will not be overwritten)
./aqua.sh clean <- Remove everything, including configuration files
./aqua.sh downloadonly <- Download using one of above options, but don't unstall

Noticed this was an issue with a prior build, 2.2.x but it looks like it was fixed.

[ballle98]

do you have any logs for what was happening right before the segv?

If you could capture a core dump then open it with gdb and get a backtrace that would be awesome
https://github.com/ballle98/AqualinkD/wiki#enable-core-dumps