I have an issue originating with an unstable clock but know this is probably hardware related. I’ll debug and figure out the offending hardware; that is not the purpose of this post.
When I encounter the unstable clock issue, I see in the logs that dump1090 stops sending to piaware and eventually piaware attempts to repair the system and restart dump1090 (which BTW a service restart does resolve the lack of sending). The problem however is that piaware is unable to locate the service if I’m interpreting the log message correctly, but the very next line is references ‘dump1090-mutabi’.
Feb 26 23:35:00 piaware piaware: attempting to restart dump1090.. Feb 26 23:35:01 piaware piaware: can't restart dump1090, no services that look like dump1090 found Feb 26 23:35:11 piaware piaware: ADS-B data program 'dump1090-mutabi' is listening on port 30005, so far so good
The question is why can’t piaware find the service? Manually, I’m able to restart dump1090-mutability.service via systemctl or the service command.
Related to permissions? (Don’t think so, but…?)
#allow-auto-updates no # using default value
allow-manual-updates yes # value set at /boot/piaware-config.txt:4
My setup is via package installs: Piaware 3.3.0 and dump1090-mutability 1.15~dev on RPi2 v1.1 and using blue FA dongle (amp/filter).