Archived: Feed issues with 19-2

[fr24-pad]

Your test for the type of installation "receiver=" can still fail.

if grep -q "^receiver.*dvbt" /etc/fr24feed.ini - will match "receiver=avr-tcp #dvb" which is a valid way to edit the config file. A better idea might be:

. /etc/fr24feed.ini
if [ "$receiver" = dvbt ] ...

Also, you are still setting a directory (/run/dump1090-mutability) to 777 permissions. Not safe. You should only create /run/fr24feed and /run/dump1090-mutability if they're required. In an installation using a stand-alone dump1090 they are not needed.

Changing directory ownership and permissions of the files from one package from the systemd config of another is not a good idea. It can, and has, broken many things.

[abcd567]

YESTERDAY
Re-imaged Raspbian Stretch Lite
Installed dump1090-mutability v1.15~dev manually (click here)
Installed fr24feed by bash script

pi@raspberrypi:~ $ sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)"
.............
[COLOR="#FF0000"]gpg: keyserver receive failed: Server indicated a failure[/COLOR]

GPG key problem encountered on STRETCH only, NOT on JESSIE.
Solved GPG key problem by manually installing the key (had to switch from pi to root to install the key)

pi@raspberrypi:~ $ sudo passwd root
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
pi@raspberrypi:~ $ su root
Password:
root@raspberrypi:/home/pi# gpg --keyserver pool.sks-keyservers.net --recv-keys 40C430F5
root@raspberrypi:/home/pi# gpg --armor --export 40C430F5 | apt-key add -  
root@raspberrypi:/home/pi# mv /etc/apt/sources.list /etc/apt/sources.list.bak 
root@raspberrypi:/home/pi# grep -v flightradar24 /etc/apt/sources.list.bak > /etc/apt/sources.list || echo OK
root@raspberrypi:/home/pi# echo 'deb http://repo.feed.flightradar24.com flightradar24 raspberrypi-stable' >> /etc/apt/sources.list

Ran perfectly well after following fix:

sudo nano /etc/systemd/system/fr24feed.service 
#changed nobody:nogroup to dump1090:nogroup in line 12

TODAY
UPDATED FROM 1.0.19-5 to 1.0.19-6

 
sudo apt-get update
apt-cache policy fr24feed
fr24feed:
  [COLOR="#FF0000"]Installed: 1.0.19-5
  Candidate: 1.0.19-6[/COLOR]

cd  /usr/lib/fr24/
sudo ./fr24feed_updater.sh

sudo apt-get update
apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.19-6
  Candidate: 1.0.19-6

FR24 1.0.19-6 on Stretch - Status.png FR24 1.0.19-6 on Stretch - map.png

Running perfectly well WITHOUT any fix. Yesterday's fix in ver 1.0.19-5 in file /etc/systemd/system/fr24feed.service disappeared after update, and still everything is running perfectly well. Rebooted to make sure, still no problem. Here is the current fr24feed.service file

cat /etc/systemd/system/fr24feed.service

[Unit]
Description=Flightradar24 Decoder & Feeder
After=network-online.target

[Service]
Type=simple
Restart=always
LimitCORE=infinity
ExecStartPre=-/usr/lib/fr24/install_dump1090.sh
ExecStartPre=-/bin/mkdir -p /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /var/log/lighttpd
ExecStartPre=-/bin/touch /dev/shm/decoder.txt
ExecStartPre=-/bin/chown -R nobody:nogroup /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt
ExecStartPre=-/bin/chmod a+rwx /run/dump1090-mutability
ExecStart=/usr/bin/fr24feed
User=nobody
Group=nogroup
PermissionsStartOnly=true
StandardOutput=null

[Install]
WantedBy=multi-user.target

[Oblivian]

Managed to break mine now

Similar spec, Piaware is happy again with .15-dev running, as is onboard map. But fr24feed won't connect to receiver out in either visual or service despite "Receiver: beast-tcp, Connected" on the web status

Only difference is I did a apt-get install vs the bash. Seeing if it makes a difference now

/edit.. ooh. Might be localhost no longer resolving. Which is probably a localised issue.. rejected by the setup wizard during setup 2nd time around and bash install

And away again with all green this time (as avr client). Go figure

[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2018-01-24 10:57:03.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-NZCH26.
[ ok ] FR24 Tracked AC:.
[ ok ] Receiver: connected ( MSGS/ SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 0.

Change back to 'localhost:30002' as source..

[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2018-01-24 10:54:22.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-NZCH26.
[ ok ] FR24 Tracked AC:.
[FAIL] Receiver: down ... failed!
[FAIL] FR24 MLAT: not running ... failed!


pi@raspberrypi:/usr/lib/fr24 $ cat /etc/hosts
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

Needs confirming, but may be a gotcha for jessies?

[hazchem]

Additionally to what Oblivian suggested, it would be very helpful to get output of the following commands please:

cat /etc/default/dump1090-mutability

fr24feed --version

cat /var/log/fr24feed/fr24feed.log

cat /dev/shm/decoder.txt

ls -al /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt /run/dump1090-mutability

ps aufx | grep -e fr24 -e dump1090

sudo systemctl status fr24feed

sudo grep -e fr24feed -e dump1090 /var/log/syslog

cat: /etc/default/dump1090-mutability: No such file or directory

1.0.19-6

cat: /var/log/fr24feed/fr24feed.log: No such file or directory

ac_map_size=3072
build_arch=static_arm
build_flavour=generic
build_os=Linux
build_revision=HEAD-635eb0b.git
build_timetamp=Jan 23 2018 08:17:49
build_version=1.0.19-6
cfg_baudrate=
cfg_bs=yes
cfg_host=
cfg_mpx=no
cfg_path=
cfg_raw=yes
cfg_receiver=dvbt
cfg_windowmode=0
d11_map_size=0
feed_alias=T-EIKN3
feed_configured_mode=UDP
feed_current_mode=UDP
feed_current_server=83.140.21.87
feed_last_attempt_time=1516794575
feed_last_config_attempt=1516794575
feed_last_config_info=
feed_last_config_result=success
feed_last_connected_time=1516794575
feed_status=connected
feed_status_message=
fr24key=bd66fb03752584ad
last_json_utc=1516794781
last_rx_connect_status=OK
last_rx_connect_time=1516794852
last_rx_connect_time_s=2018-01-24 11:54:06


pi 21925 0.0 0.3 2668 1376 pts/1 S+ 11:56 0:00 \_ grep --color=auto -e fr2 -e dump1090
root 19340 0.0 0.5 4600 2600 ? S 09:42 0:00 sudo fr24feed
root 19347 0.1 1.3 106724 5812 ? Sl 09:42 0:12 \_ fr24feed
nobody 21491 0.1 0.7 106724 3500 ? Ssl 11:49 0:00 /usr/bin/fr24feed




mlat-ok=NO
mlat-started=YES
mlat_problem=no-config
msg_ring_full=0
msg_ring_length=0
offline-mode=no
rx_connected=0
shutdown=no
time_update_utc=1516794823
time_update_utc_s=2018-01-24 11:53:43
timing_is_valid=1
timing_last_drift=-0.0011
timing_last_offset=-0.0011
timing_last_result=success
timing_source=NTP
timing_time_last_attempt=1516794575
timing_time_last_success=1516794575
timing_time_since_last_success=1516794575

-rw-r--r-- 1 nobody nogroup 1162 Jan 24 11:55 /dev/shm/decoder.txt

/run/dump1090-mutability:
total 0
drwxrwxrwx 2 root root 40 Jan 24 07:05 .
drwxr-xr-x 19 root root 640 Jan 24 07:05 ..

/run/fr24feed:
total 0
drwxr-xr-x 2 nobody nogroup 40 Jan 24 07:05 .
drwxr-xr-x 19 root root 640 Jan 24 07:05 ..

/var/log/fr24feed:
total 0
drwxr-xr-x 2 nobody nogroup 40 Jan 24 07:05 .
drwxr-xr-x 5 root root 280 Jan 24 07:05 ..


Jan 23 15:27:15 raspberrypi fr24feed[514]: Starting FR24 feeder: fr24feed.
Jan 24 07:00:01 raspberrypi CRON[16472]: (root) CMD (/usr/lib/fr24/fr24feed_updater.sh >/dev/null 2>&1)
Jan 24 07:03:23 raspberrypi fr24feed[16546]: Stopping FR24 feeder: fr24feed.
Jan 24 07:05:47 raspberrypi systemd[1]: fr24feed.service start-pre operation timed out. Terminating.
Jan 24 07:05:47 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
Jan 24 07:05:47 raspberrypi systemd[1]: fr24feed.service holdoff time over, scheduling restart.
Jan 24 07:07:18 raspberrypi systemd[1]: fr24feed.service start-pre operation timed out. Terminating.
Jan 24 07:07:18 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
Jan 24 07:07:18 raspberrypi systemd[1]: fr24feed.service holdoff time over, scheduling restart.
Jan 24 07:08:48 raspberrypi systemd[1]: fr24feed.service start-pre operation timed out. Terminating.
Jan 24 07:08:49 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
Jan 24 07:08:49 raspberrypi systemd[1]: fr24feed.service holdoff time over, scheduling restart.

[Guest]

Looks like you've missed one command:

sudo systemctl status fr24feed

Also could you please execute these:

ls -al /usr/lib/fr24

cat /etc/fr24feed.ini | grep -v fr24key

/usr/lib/fr24/dump1090 --help 2>&1 | grep dump1090

[hazchem]

Looks like you've missed one command:



Also could you please execute these:

Oops sorry
● fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled)
Active: active (running) since Wed 2018-01-24 11:49:24 UTC; 33min ago
Process: 21488 ExecStartPre=/bin/chmod a+rwx /run/dump1090-mutability (code=exited, status=0/SUCCESS)
Process: 21485 ExecStartPre=/bin/chown -R nobody:nogroup /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt (code=exited, status=0/SUCCESS)
Process: 21482 ExecStartPre=/bin/touch /dev/shm/decoder.txt (code=exited, status=0/SUCCESS)
Process: 21476 ExecStartPre=/bin/mkdir -p /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /var/log/lighttpd (code=exited, status=0/SUCCESS)
Process: 21448 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=100)
Main PID: 21491 (fr24feed)
CGroup: /system.slice/fr24feed.service
└─21491 /usr/bin/fr24feed

Jan 24 11:49:24 raspberrypi systemd[1]: Started Flightradar24 Decoder & Feeder.

Thanks

receiver="dvbt"
bs="yes"
raw="yes"
logmode="0"
windowmode="0"
mpx="no"
mlat="yes"
mlat-without-gps="yes"


-bash: /usr/lib/fr24/dump1090: No such file or directory



total 24
drwxr-xr-x 3 pi pi 4096 Jan 24 07:04 .
drwxr-xr-x 39 root root 4096 Apr 24 2017 ..
-rwxr-xr-x 1 root root 1127 Mar 2 2016 activate-cron.sh
-rwxr-xr-x 1 root root 1264 Jan 23 08:17 fr24feed_updater.sh
-rwxr-xr-x 1 root root 1237 Jan 23 08:17 install_dump1090.sh
drwxr-xr-x 3 pi pi 4096 Jan 24 07:04 public_html

[Guest]

Thanks, we are getting closer. Seems that dump1090 installation script fails for you.
Could you please run:

sudo /usr/lib/fr24/install_dump1090.sh

and post the output?

[mgunther]

Hello everyone,

Sorry for the latest disruptions and thanks a lot for your feedback, it is absolutely valuable and helpful!
As you see, there are lots of different platforms to support and even automated testing doesn't always find all possible issues. But we are working hard!

Regarding NTP or similar issues - we have an RPi unit running Jessie but can't reproduce any issues with running fr24feed as nobody. Could you please provide more details, was the OS somehow modified, e.g. security-wise?

I don't think the OS was modified - and if it was, it was not done on purpose. It had been running for well over a year with regular updates being applied. If you want me to check something specific, let me know please and I can have a look later this evening.

Edit: actually I remember now that I messed with the name resolution settings (likely to use Google 8.8.8.8). But I need to confirm that in the evening.

In the meantime, I see this:

https://wiki.debian.org/SystemGroups

nogroup (user: nobody): Daemons that need not own any files run as user nobody and group nogroup. Thus, no files on a system should be owned by this user or group.

Maybe it is not such a good idea to use the nobody/nogroup settings?

[hazchem]

dump1090 is not found, downloading dump1090-mutability...
info: Trying to set 'dump1090-mutability/auto-start' [boolean] to 'false'
info: Loading answer for 'dump1090-mutability/auto-start'
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://repo.feed.flightradar24.com flightradar24 InRelease
Hit http://archive.raspberrypi.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable armhf Packages
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Ign http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable Translation-en
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

[Guest]

Can you please run "sudo dpkg --configure -a" and post the output here? It would be invaluable to understand the problem as I can't reproduce it here.

[k5hmd]

I allowed mine to update this morning and it's broke again. Not as bad as I can still access it via a browser. Here's the results of the "sudo dpkg --configure -a"

pi@raspberrypi:~ $ sudo dpkg --configure -a
Setting up fr24feed (1.0.19-6) ...

Configuration file '/etc/fr24feed.ini'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.

[YoshiH]

Can you please run "sudo dpkg --configure -a" and post the output here? It would be invaluable to understand the problem as I can't reproduce it here.

dpkg: error: unable to access dpkg status area: Read-only file system

[Guest]

We've published a beta version 1.0.19-7. Feel free to give it a try. It should overcome "dpkg --configure" issue and will run from fr24:fr24 user instead of nobody:nogroup (as this seems to be causing problems to some installations). Your feedback is appreciated.

To install beta version, edit file /etc/apt/sources.list and change "raspberrypi-stable" to "raspberrypi-beta".
Then run:

sudo apt-get update
sudo /usr/lib/fr24/fr24feed_updater.sh

[YoshiH]

Would love to, but with saving I get [ Error writing /etc/apt/sources.list: Read-only file system ].

[Guest]

That means your SD card is mounted in read only mode. To remount it, run:

sudo mount -o remount,rw /