Fr24feed refueses to run as a service or systemctl

[Aviator77x]

However when I start just fr24feed from terminal it works fine.

This is the result of the autostart:

2020-04-22 16:53:52 | [main][i]FR24 Feeder/Decoder
2020-04-22 16:53:52 | [main][i]Version: 1.0.18-5/generic
2020-04-22 16:53:52 | [main][i]Built on Mar 4 2016 16:26:55 (devel-d11ca48.git/Linux/x86_64)
2020-04-22 16:53:52 | [main][i]Copyright 2012-2016 Flightradar24 AB
2020-04-22 16:53:52 | [main][i]http://flightradar24.com
2020-04-22 16:53:52 | [main][i]DNS mode: LIBC/PING
2020-04-22 16:53:52 | [main][i]Automatic updates are DISABLED
2020-04-22 16:53:52 | ERROR
2020-04-22 16:53:52 | [main][i]Reader thread started
2020-04-22 16:53:52 | [main][i]Socket server started
2020-04-22 16:53:52 | [main][i]MLAT data feed started
2020-04-22 16:53:52 | [httpd][i]Server started, listening on 0.0.0.0:8754
2020-04-22 16:53:52 | [mlat][i]Waiting for MLAT configuration
2020-04-22 16:53:52 | [bs][i]Initializing server
2020-04-22 16:53:52 | [bs][i]Starting server on 0.0.0.0:30003
2020-04-22 16:53:52 | [reader][i]Initializing reader
2020-04-22 16:53:52 | [reader][i]Connecting to Beast receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat XX.8897 --lon XX.6176 --raw --mlat)
2020-04-22 16:53:52 | [reader][i]Connected to the receiver, configuring
2020-04-22 16:53:52 | [reader][i]Configured, processing messages
2020-04-22 16:53:52 | [master][i]Starting processing thread
2020-04-22 16:53:53 | [reader][i]Connection terminated
2020-04-22 16:53:53 | [main][i]Terminating child process 967 with SIGETERM
2020-04-22 16:53:53 | [time][i]Synchronizing time via NTP

Problems started after updating ubuntu to the latest LTS

[Oblivian]

If you let it go some more, I suspect it's not starting there either, and you will see more of this

2020-04-22 16:53:52 | [master][i]Starting processing thread
2020-04-22 16:53:53 | [reader][i]Connection terminated
2020-04-22 16:53:53 | [main][i]Terminating child process 967 with SIGETERM

Which means it's probably not connecting to decoder as expected using that commandline.

[Aviator77x]

If you let it go some more, I suspect it's not starting there either, and you will see more of this

2020-04-22 16:53:52 | [master][i]Starting processing thread
2020-04-22 16:53:53 | [reader][i]Connection terminated
2020-04-22 16:53:53 | [main][i]Terminating child process 967 with SIGETERM

Which means it's probably not connecting to decoder as expected using that commandline.

This is the log from when fr24feed started atomatically at boot. After stopping the process and running it in a terminal window it works perfectly, its just when I run it as a service or systemctl it refuses to work.