I’ve been seamlessly running piaware 2.1.5 for months. I’ve updated to the latest 3.1.0 version, and finally managed to make it work, especially dump1090-fa which would not start at boot unless I put a script in init.d.
Now it’s running, feeders to FA and FR24 too, MLAT is running and reporting positions as well. My point is, the local dump1090 map does not work.
The page loads, there’s a map too, and a message “problem fetching data from dump1090”
I tried to sort this out to not avail, I get there’s an aircraft.json file I used for the local display (unless I got it wrong), alas there’s no such file on my raspi.
Piaware status as follows:
PiAware master process (piaware) is running with pid 19736.
PiAware ADS-B client (faup1090) is running with pid 20915.
PiAware mlat client (fa-mlat-client) is running with pid 19788.
Local ADS-B receiver (dump1090-fa) is running with pid 20852.
dump1090-fa (pid 20852) is listening for connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.
dump1090 is producing data on localhost:30005.
Is there something to create and/or feed that aircraft.json file? Is there a parameter to pass upon dump1090 startup?
I started with a classic raspbian wheezy, updated to jessie with apt-get update, then had to remove the piaware package and dump1090 (apt-get remove, then purge) ;
reinstalled both 3.1.0 package and dump1090-fa with apt as told in the update page.
Ok, so with that setup you should not need an init.d script at all, the Jessie package includes a systemd service. It includes the right parameters to write the json file where it’s needed. You should investigate why the dump1090-fa systemd service isn’t starting correctly (“systemctl status dump1090-fa” and “journalctl -u dump1090-fa” are good starting points)
I guess it is probably the wheezy → jessie upgrade that means you’re on sysv. I haven’t tested the jessie packages against a system configured that way which will be why you’re running into this. In theory I can include the wheezy init.d script in the jessie package too (and I think it is ignored if systemd is in use), I will look into that.
That was it. After replacing SysV with systemd, removing my start script and rebooting the pi, the services turned on and I had feeder and local dump1090 display running.
Now I’m having boot issues, but that’s system related and I’ll iron this out by myself.
Thank you for your help and tips! You’ve got me on the right way.
