FlightAware Discussions

[SOLVED] Log output missing

I followed the instructions and compiled dump1090 and piaware on StretchARM64 on an Odroid N2. Feeds like a charm, except it appears that the log-files are not created for airspy_adsb, dump1090. It is created for piaware.

When I reboot the N2 everything looks normal, but after a brief period of time I see this:

root@odroid-stretch64 : ~ # systemctl status dump1090-fa
dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-07-08 15:31:42 PDT; 1 day 4h ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 2158 (dump1090-fa)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/dump1090-fa.service
└─2158 /usr/bin/dump1090-fa --net-only --max-range 360 --net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --lat 37.53022 --lon -122.29481 --write-json /run/dump1090-fa --quiet

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
root@odroid-stretch64 : ~ # journalctl -eu dump1090
– No entries –
root@odroid-stretch64 : ~ #

Similarly, for airspy_adsb I get no love. piaware actually does give some more accurate but is not clear where it gets its input from, like this (emphasis added):

Jul 09 19:19:05 odroid-stretch64 piaware[2163]: 2153006 msgs recv’d from unknown process (4003 in last 5m); 2147260 msgs sent to FlightAware

Is there some setting I need to change?

You are missing suitable sudo rules to allow the user that piaware runs as to run netstat as root.

One of these things is not like the other.

Could be low disk space or some other program spamming the system journal (log).

root@pi ~  journalctl
-- Logs begin at Thu 2019-07-04 07:10:24 UTC, end at Wed 2019-07-10 04:27:04 UTC. --

Might be low disk space and journalctl is not keeping messages very long because it’s limited to short timespan.
Might be the memory is full and journal persistence is off, thus it needs to delete old log files.

Also dump1090 is not a service you are using, it will have no log as obj pointed out.

There is no sudo installed on StretchARM64 on Odroid. So, I installed it separately. That seems to work for now.

root@odroid-stretch64 : ~ # apt-cache policy sudo
Installed: (none)
Candidate: 1.8.19p1-2.1
Version table:
1.8.19p1-2.1 500
500 http://ftp.uk.debian.org/debian stretch/main arm64 Packages
root@odroid-stretch64 : ~ # apt install sudo

Let’s see if that was it.
I actually did not even realize that sudo is just a package.

The unknown process thing is still present.

Adding sudo (might need piaware purge and reinstall) will only fix the “from unkown process” to change to dump1090-fa or whatever.
No real information win you should already know which program is listening on the port you are pointing piaware to.

Won’t fix your other problem with the log.

Did a restart yesterday.

Indeed that one got resolved with the install of sudo.

That does indeed still exist. It’s fine for a few hours and then the message comes back.

in itself I do not care too much about the lack of log-files as long as nothing goes awry…

Did you read that you specified the wrong service?

journalctl -eu dump1090
journalctl -eu dump1090-fa

There are basically no logs after dump1090-fa and airspy_adsb get started.
So do a restart for both services and check then:

systemctl restart dump1090-fa airspy_adsb
journalctl -eu dump1090-fa
journalctl -eu airspy_adsb

I am sorry about the typo.

I changed the /etc/systemd/journalconfd to persistent (from auto) and restarted the journal. For now I am back in the journal business.

Seems I managed to solve the missing log files.
Solution was to change in the file /etc/systemd/journald.conf the line #Storage=auto to Storage=persistent (note the removal of the hash). Then restart the daemon:
systemctl restart systemd-journald
In essence, it saves the logs on the sd-card rather than in memory.