Tweet
Apologies for starting yet another thread, but from where I'm sitting the problem with Pi updates still isn't fixed.
At about 0700 on 16th Jan my Pi stopped reporting along with many others. Not realising there was a general problem I just downloaded a new image (.18-9) and started again. Then I started following the issue here and understood why my Pi had failed. Interestingly my Pi never updated itself to a 19-* version after the re-install on the 16th, it just kept working.
Having read that the problems looked as if they were resolved, last night I installed a new image (18-9 again) and left it running to see if it would update. At about 0700 today it stopped reporting. Status report is below.
So - I've re-installed yet again (18-9), and I'm up and running. I've commented out the line in /etc/cron.d/fr24feed_updater in the hope that I don't end up doing this every day.
The only change I make to my installations is to add the --net argument to dump1090, via the settings page on the FR24 Feeder Status web interface, so I can use the map. It seems to me that if a vanilla install of fr24feed stops working following a scheduled update, then all is not well. I'm not a Linux guru although I can tinker a bit, but for a naïve user I'm afraid this still look broken to me. I don't think there's anything odd about my set-up - there's nothing else running on this Pi.
=====================
pi@raspberrypi:~ $ sudo service fr24feed status
â fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled)
Active: failed (Result: start-limit) since Wed 2018-01-31 07:07:04 UTC; 2h 5min ago
Process: 11298 ExecStart=/usr/bin/fr24feed (code=exited, status=217/USER)
Process: 11295 ExecStartPre=/bin/chmod a+rwx /run/dump1090-mutability (code=exited, status=217/USER)
Process: 11292 ExecStartPre=/bin/chown -R fr24:fr24 /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt (code=exited, status=217/USER)
Process: 11289 ExecStartPre=/bin/touch /dev/shm/decoder.txt (code=exited, status=217/USER)
Process: 11286 ExecStartPre=/bin/mkdir -p /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /var/log/lighttpd (code=exited, status=217/USER)
Process: 11283 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=217/USER)
Process: 11280 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=217/USER)
Main PID: 11298 (code=exited, status=217/USER)
Jan 31 07:07:04 raspberrypi systemd[1]: fr24feed.service holdoff time over, ....
Jan 31 07:07:04 raspberrypi systemd[1]: Stopping Flightradar24 Decoder & Fee....
Jan 31 07:07:04 raspberrypi systemd[1]: Starting Flightradar24 Decoder & Fee....
Jan 31 07:07:04 raspberrypi systemd[1]: fr24feed.service start request repea....
Jan 31 07:07:04 raspberrypi systemd[1]: Failed to start Flightradar24 Decode....
Jan 31 07:07:04 raspberrypi systemd[1]: Unit fr24feed.service entered failed....
Hint: Some lines were ellipsized, use -l to show in full.
pi@raspberrypi:~ $
=====================
At about 0700 on 16th Jan my Pi stopped reporting along with many others. Not realising there was a general problem I just downloaded a new image (.18-9) and started again. Then I started following the issue here and understood why my Pi had failed. Interestingly my Pi never updated itself to a 19-* version after the re-install on the 16th, it just kept working.
Having read that the problems looked as if they were resolved, last night I installed a new image (18-9 again) and left it running to see if it would update. At about 0700 today it stopped reporting. Status report is below.
So - I've re-installed yet again (18-9), and I'm up and running. I've commented out the line in /etc/cron.d/fr24feed_updater in the hope that I don't end up doing this every day.
The only change I make to my installations is to add the --net argument to dump1090, via the settings page on the FR24 Feeder Status web interface, so I can use the map. It seems to me that if a vanilla install of fr24feed stops working following a scheduled update, then all is not well. I'm not a Linux guru although I can tinker a bit, but for a naïve user I'm afraid this still look broken to me. I don't think there's anything odd about my set-up - there's nothing else running on this Pi.
=====================
pi@raspberrypi:~ $ sudo service fr24feed status
â fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled)
Active: failed (Result: start-limit) since Wed 2018-01-31 07:07:04 UTC; 2h 5min ago
Process: 11298 ExecStart=/usr/bin/fr24feed (code=exited, status=217/USER)
Process: 11295 ExecStartPre=/bin/chmod a+rwx /run/dump1090-mutability (code=exited, status=217/USER)
Process: 11292 ExecStartPre=/bin/chown -R fr24:fr24 /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt (code=exited, status=217/USER)
Process: 11289 ExecStartPre=/bin/touch /dev/shm/decoder.txt (code=exited, status=217/USER)
Process: 11286 ExecStartPre=/bin/mkdir -p /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /var/log/lighttpd (code=exited, status=217/USER)
Process: 11283 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=217/USER)
Process: 11280 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=217/USER)
Main PID: 11298 (code=exited, status=217/USER)
Jan 31 07:07:04 raspberrypi systemd[1]: fr24feed.service holdoff time over, ....
Jan 31 07:07:04 raspberrypi systemd[1]: Stopping Flightradar24 Decoder & Fee....
Jan 31 07:07:04 raspberrypi systemd[1]: Starting Flightradar24 Decoder & Fee....
Jan 31 07:07:04 raspberrypi systemd[1]: fr24feed.service start request repea....
Jan 31 07:07:04 raspberrypi systemd[1]: Failed to start Flightradar24 Decode....
Jan 31 07:07:04 raspberrypi systemd[1]: Unit fr24feed.service entered failed....
Hint: Some lines were ellipsized, use -l to show in full.
pi@raspberrypi:~ $
=====================