Archived: Feed issues with 19-2

[RockRidge]

I’m not real technical but I’m reading all the post and trying to keep up.

FR24 tech support had me run:
sudo apt update
sudo apt remove dump1090-mutability fr24feed
sudo rm -f /etc/default/dump1090-mutability
sudo rm -f /etc/udev/rules.d/rtl-sdr.rules
sudo apt install fr24feed

I’m feeding data to them but I lost my local access map Dump1090 and performance graphs.
Not what I wanted to happen!
Do I need to reimage and start again?

[YoshiH]

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

sudo mount -o remount,rw /

Flightradar24 Feeder/Decoder

Linux/generic/static_arm/1.0.19-7

Updated: 19:43:19 GMT+0100 (CET)

FR24 Link:	Connected via UDP
FR24 Radar Code:	T-EHLE86
Aircraft Tracked (ModeS & ADS-B):	0
Aircraft Uploaded:	N/A
Receiver:	dvbt, Connected
MLAT running:	NO

ac_map_size="3072"
build_arch="static_arm"
build_flavour="generic"
build_os="Linux"
build_revision="HEAD-407b76d.git"
build_timetamp="Jan 24 2018 14:33:56"
build_version="1.0.19-7"
cfg_baudrate=""
cfg_bs="yes"
cfg_host=""
cfg_mpx="no"
cfg_path="/usr/lib/fr24/dump1090"
cfg_raw="yes"
cfg_receiver="dvbt"
cfg_windowmode="0"
d11_map_size="0"
feed_alias="T-EHLE86"
feed_configured_mode="UDP"
feed_current_mode="UDP"
feed_current_server="83.140.21.87"
feed_last_attempt_time="1516819341"
feed_last_config_attempt="1516819341"
feed_last_config_info=""
feed_last_config_result="success"
feed_last_connected_time="1516819341"
feed_status="connected"
feed_status_message=""
fr24key="Removed_My_Key"
last_json_utc="1516819381"
last_rx_connect_status="OK"
last_rx_connect_time="1516819446"
last_rx_connect_time_s="2018-01-24 18:44:06"
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="1516819409"
time_update_utc_s="2018-01-24 18:43:29"
timing_is_valid="1"
timing_last_drift="-0.0005"
timing_last_offset="-0.0005"
timing_last_result="success"
timing_source="NTP"
timing_time_last_attempt="1516819341"
timing_time_last_success="1516819341"
timing_time_since_last_success="1516819341"

I cannot post link to pastebin yet...

[mgunther]

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:

Done that but still the same problem for me even with fr24:fr24 user: Unable to connect to localhost, unable to synchronize time and unable to connect to feed.flightradar24.com. The only user that works on my system is root.

I'll try to do a bit of digging and see if I can find a reason for that behaviour.

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

sudo mount -o remount,rw /

[YoshiH]

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

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]

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

[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.

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.

[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.

[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?

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?

[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

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]

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.