kplex.service: Failed with result 'signal'

[marcus-aa]

We are getting this error on a couple of the units running kplex. Systemctl does not re-start from this condition so all the data feed is lost until manually restarted.

Simple config with a USB AIS receiver, sending data to 2 remote TCP servers.

Any idea what causes this or why the error is not handled?

`root@P-VADERAIS:~# systemctl status kplex.service
● kplex.service - NMEA 0183 Multiplexer
Loaded: loaded (/etc/systemd/system/kplex.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sat 2022-10-29 21:17:11 CEST; 2 weeks 0 days ago
Docs: http://www.stripydog.com/kplex/configuration.html
Process: 657 ExecStart=/usr/bin/kplex -p /var/run/kplex.pid -o mode=background (code=exited, status=0/SUCCESS)
Main PID: 658 (code=killed, signal=ABRT)

Oct 29 21:17:10 P-VADERAIS systemd[1]: Starting NMEA 0183 Multiplexer...
Oct 29 21:17:10 P-VADERAIS systemd[1]: Started NMEA 0183 Multiplexer.
Oct 29 21:17:10 P-VADERAIS kplex[657]: Lookup failed for host ais.servername1.net/service 6300: Temporary failure in name resolution
Oct 29 21:17:10 P-VADERAIS kplex[657]: Lookup failed for host ais.servername2.net/service 10003: Temporary failure in name resolution
Oct 29 21:17:10 P-VADERAIS kplex[657]: munmap_chunk(): invalid pointer
Oct 29 21:17:11 P-VADERAIS systemd[1]: kplex.service: Main process exited, code=killed, status=6/ABRT
Oct 29 21:17:11 P-VADERAIS systemd[1]: kplex.service: Failed with result 'signal'.
`

[stripydog]

Apologies for the delay. I believe this may be a duplicate of #49. If so this is fixed in the develop branch (and in fact has been for 2 years). If you have the ability to compile develop, it should hopefully fix it. Yes a new release is long overdue. insane work and family pressures have stopped me doing much "leisure coding" these days