Today I compiled & ran it on raspbian buster, and it works ok
I should add that the only other difference from the Raspbian Stretch / Dump1090-mutability old SD card to the new Raspbian Buster / Dunp1090-fa new SD card (in so far as ppup) is that the new one is using your “alternate (and better) method to start ppup1090 at boot is to create ppup1090.service file and enable it, so that ppup1090 is started by systemd”, whereas the old SD card was using the rc.local option to start.
Not sure whether this could be part of the problem.
Lets see what tonight (UK time) brings.
I have used both the rc.local method of the first post, and ppup1090.service method of post quoted below. Both work flawlessly and are very stable. I dont think the cause of failure was due to using systemd service.
The systemd service method has advantage that it gives easy control to stop, start, restart, and monitor the status.
Update…
For the third successive night, I received a PlanePlotter RPi inactivity alert e-mail, sent at exactly 04:11 on all three nights, relating to my RPi3B sharecode Z1.
As I have registered for an alert e-mail following two hours of inactivity, this suggests 02:11 (UTC . UK local time), but http://www.coaa.co.uk/sharerlocations.txt suggests that this occurred at 02:40.
So, I really need to work out what the heck is happening to ppup1090 every night!!! Dump1090-fa and uploads to FR24 and Plane Finder are still working perfectly.
Interestingly, ppup1090 is still running on the RPi in question, but is now top of the list when one executes ‘top’.
Ian
It’s using 100% cpu which it shouldn’t, so there’s something wrong with it. Kill it and restart it.
Yep, did that and been OK ever since. Probably will stay fine until 2:00 ish in the morning. A bit of a puzzle!
Please post output of following command:
sudo journalctl -eu ppup1090
I am thinking that this does not look good?
– Logs begin at Thu 2019-02-14 10:11:59 GMT, end at Thu 2019-12-12 17:46:54 GMT. –
– No entries –
Try this:
sudo journalctl -eu ppup1090 --no-pager
This is what I get
pi@raspberrypi:~ $ sudo journalctl -eu ppup1090 --no-pager
-- Logs begin at Thu 2019-02-14 05:12:00 EST, end at Thu 2019-12-12 12:54:50 EST. --
Dec 12 12:46:12 raspberrypi systemd[1]: Started PlanePlotter Raspberry Pi uploader.
Dec 12 12:46:12 raspberrypi ppup1090[762]: Failed to connect to 127.0.0.1:30005
Dec 12 12:46:12 raspberrypi systemd[1]: ppup1090.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 12:46:12 raspberrypi systemd[1]: ppup1090.service: Failed with result 'exit-code'.
Dec 12 12:46:53 raspberrypi systemd[1]: ppup1090.service: Service RestartSec=30s expired, scheduling restart.
Dec 12 12:46:53 raspberrypi systemd[1]: ppup1090.service: Scheduled restart job, restart counter is at 1.
Dec 12 12:46:53 raspberrypi systemd[1]: Stopped PlanePlotter Raspberry Pi uploader.
Dec 12 12:46:53 raspberrypi systemd[1]: Started PlanePlotter Raspberry Pi uploader.
pi@raspberrypi:~ $ sudo systemctl status ppup1090
● ppup1090.service - PlanePlotter Raspberry Pi uploader
Loaded: loaded (/lib/systemd/system/ppup1090.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-12-12 12:46:53 EST; 11min ago
Main PID: 1226 (ppup1090)
Tasks: 3 (limit: 2200)
Memory: 2.9M
CGroup: /system.slice/ppup1090.service
└─1226 /home/pi/ppup/ppup1090 --quiet
Dec 12 12:46:53 raspberrypi systemd[1]: Started PlanePlotter Raspberry Pi uploader.
100% CPU usage
.
Something wrong. I get only 0.7 % CPU usage
(In screenshot below, dont get confused by duplicate entries of dump1090-mutab, piaware, fr24feed, pfclient mlat-client etc. I have TWO independent receivers running on single Pi
)
Same again unfortunately:
pi@RaspberryPi3:~ $ sudo journalctl -eu ppup1090 --no-pager
– Logs begin at Thu 2019-02-14 10:11:59 GMT, end at Thu 2019-12-12 18:21:02 GMT. –
– No entries –
What is output of this command?
sudo systemctl status ppup1090
Just redone this:
pi@RaspberryPi3:~ $ sudo journalctl -eu ppup1090 --no-pager
– Logs begin at Thu 2019-12-12 18:45:57 GMT, end at Thu 2019-12-12 18:47:50 GMT. –
Dec 12 18:46:02 RaspberryPi3 systemd[1]: Started PlanePlotter Raspberry Pi uploader.
Dec 12 18:46:02 RaspberryPi3 ppup1090[439]: Failed to connect to 127.0.0.1:30005
Dec 12 18:46:02 RaspberryPi3 systemd[1]: ppup1090.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 18:46:02 RaspberryPi3 systemd[1]: ppup1090.service: Failed with result ‘exit-code’.
Dec 12 18:46:32 RaspberryPi3 systemd[1]: ppup1090.service: Service RestartSec=30s expired, scheduling restart.
Dec 12 18:46:32 RaspberryPi3 systemd[1]: ppup1090.service: Scheduled restart job, restart counter is at 1.
Dec 12 18:46:32 RaspberryPi3 systemd[1]: Stopped PlanePlotter Raspberry Pi uploader.
Dec 12 18:46:32 RaspberryPi3 systemd[1]: Started PlanePlotter Raspberry Pi uploader.
And:
pi@RaspberryPi3:~ $ sudo systemctl status ppup1090
- ppup1090.service - PlanePlotter Raspberry Pi uploader
Loaded: loaded (/lib/systemd/system/ppup1090.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-12-12 18:46:32 GMT; 2min 56s ago
Main PID: 1154 (ppup1090)
Tasks: 3 (limit: 2200)
Memory: 11.0M
CGroup: /system.slice/ppup1090.service
`-1154 /home/pi/ppup/ppup1090 --quiet
Dec 12 18:46:32 RaspberryPi3 systemd[1]: Started PlanePlotter Raspberry Pi uploader.
All seems normal. This is same as what I get.
(1) How much CPU usage it shows now?
(2) Give all tyhese commands, and post output of last command:
sudo systemctl stop ppup1090
cd ppup
./ppup1090
After this test
sudo reboot
All your outputs show that everything is perfectly ok.
When sometimes ago I had formatted my microSD card for upgrading my system, I did not install ppup1090. Today I have installed it and left running. Will check tonight at about 1 am, and again tomorrow morning to find out if it fails or gives very high CPU usage.
Thank you very much.
About an year ago, someone else had issue of ppup1090 CPU usage 100%.
Started ppup1090 at 2:42 pm on Dec 12, checked after 10.5 hrs at 1:12 am on Dec 13. All OK
pi@raspberrypi:~ $ sudo systemctl status ppup1090
● ppup1090.service - PlanePlotter Raspberry Pi uploader
Loaded: loaded (/lib/systemd/system/ppup1090.service; enabled; vendor preset: enabl
Active: active (running) since Thu 2019-12-12 14:42:59 EST; 10h ago
Main PID: 23361 (ppup1090)
Tasks: 3 (limit: 2200)
Memory: 5.7M
CGroup: /system.slice/ppup1090.service
└─23361 /home/pi/ppup/ppup1090 --quiet
Dec 12 14:42:59 raspberrypi systemd[1]: Started PlanePlotter Raspberry Pi uploader.




