Announcement

**Colin Mair** · 2018-01-25, 15:01

I have just applied the 1.0.19.8 beta version and it is working and feeding data ok.
I undid the fix I had applied to /bin/ping by sudo chmod 755 /bin/ping prior to updating to 19.8 and can confirm that the updating process set the permissions of ping the same as sudo chmod 4755 /bin/ping did.

**mgunther** · 2018-01-25, 15:44

Originally posted by vinnyspb View Post

Just published 1.0.19-8 into beta.

I would aim to release it to stable soon-ish if no unexpected issues come up.

Changes:

- binary permissions fixed according to user reports
- force dpkg to reconfigure bad state of fr24feed
- http://RECEIVER_IP:8754/diagnostics_dump.tgz will download archive with diagnostics which can be shared with Flightradar24 support in case of something not working to facilitate diagnostics

Will upgrade later. Just wondering if it would be feasible and a good idea or not to reverse directory permissions on /run/dump1090-mutability that was set incorrectly as 'nobody:nogroup' in earlier versions for people that already had dump1090-mutability installed? Not sure if you can now detect such cases and if trying to fix would do more harm than good. But I thought I'll throw the idea out there anyway for your consideration.

**Guest** · 2018-01-25, 15:53

Originally posted by mgunther View Post

Will upgrade later. Just wondering if it would be feasible and a good idea or not to reverse directory permissions on /run/dump1090-mutability that was set incorrectly as 'nobody:nogroup' in earlier versions for people that already had dump1090-mutability installed? Not sure if you can now detect such cases and if trying to fix would do more harm than good. But I thought I'll throw the idea out there anyway for your consideration.

We can certainly try that, but the problem here is that we don't know what permissions were there before the change. So I'm afraid guessing might cause more troubles...

**mgunther** · 2018-01-25, 16:18

Yes I understand the difficulty in 'guessing'. However, the default user for pre-existing dump1090-mutability installations is 'dump1090'. Anyone who uses something different is probably a skilled Linux user who knows what they are doing and would not be easily defeated by wrongly set directory permissions in any case. Personally I don't see a reason why anyone would use anything different than 'dump1090' but I guess I could be wrong too. Food for thought maybe?

**Guest** · 2018-01-25, 16:48

Originally posted by mgunther View Post

Yes I understand the difficulty in 'guessing'. However, the default user for pre-existing dump1090-mutability installations is 'dump1090'. Anyone who uses something different is probably a skilled Linux user who knows what they are doing and would not be easily defeated by wrongly set directory permissions in any case. Personally I don't see a reason why anyone would use anything different than 'dump1090' but I guess I could be wrong too. Food for thought maybe?

Sure, need to think about that a little more.

For now I've pushed 1.0.19-8 into stable channel.

Thanks everyone for the feedback! Very appreciated!

**abcd567** · 2018-01-25, 17:58

UPGRADED TO VER 1.0.19-8 JUST NOW

STEP-1: Checked current status before upgrading

Code:

pi@raspberrypi:~ $ cat /etc/os-release
[COLOR="#FF0000"]PRETTY_NAME="Raspbian GNU/Linux 9 ([B]stretch[/B])"[/COLOR]
.........


pi@raspberrypi:~ $ apt-cache policy fr24feed
fr24feed:
  [COLOR="#FF0000"]Installed: 1.0.19-6[/COLOR]
  Candidate: 1.0.19-6
............

pi@raspberrypi:~ $ apt-cache policy dump1090-mutability
dump1090-mutability:
  [COLOR="#FF0000"]Installed: 1.15~dev[/COLOR]
  Candidate: 1.15~dev
.................

Code:

pi@raspberrypi:~ $ 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 [COLOR="#FF0000"]nobody:nogroup[/COLOR] /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt
ExecStartPre=-/bin/chmod a+rwx /run/dump1090-mutability
ExecStart=/usr/bin/fr24feed
[COLOR="#FF0000"]User=nobody[/COLOR]
[COLOR="#FF0000"]Group=nogroup[/COLOR]
PermissionsStartOnly=true
StandardOutput=null

[Install]
WantedBy=multi-user.target

STEP-2: Upgraded to 1.0.19-8

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

Code:

pi@raspberrypi:~ $ sudo apt-get update

pi@raspberrypi:~ $ apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.19-6
  Candidate: 1.0.19-8
............


pi@raspberrypi:~ $ sudo /usr/lib/fr24/fr24feed_updater.sh
[COLOR="#FF0000"]/usr/lib/fr24/fr24feed_updater.sh: line 8: /dev/mmcblk0p2: Permission denied[/COLOR]
......................
.....................
.....................
[COLOR="#FF0000"]W: GPG error: http://apt.rb24.com jessie Release: The following signatures were invalid: A7E7D5E3786CA2212A3A5F4769D62C99357DF51A
W: The repository 'http://apt.rb24.com jessie Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: No Hash entry in Release file /var/lib/apt/lists/partial/apt.rb24.com_dists_jessie_Release which is considered strong enough for security purposes
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/apt.rb24.com_dists_jessie_Release
[/COLOR]Installed version: 1.0.19-6
Latest available: 1.0.19-8
Upgrading fr24feed from 1.0.19-6 to 1.0.19-8...
...................
...................
[COLOR="#00AA00"]Unpacking fr24feed (1.0.19-8) over (1.0.19-6) ...
Setting up fr24feed (1.0.19-8) ...
Installing new version of config file /etc/cron.d/fr24feed_updater ...[/COLOR]
mount: / is busy

STEP-3: Checked after upgrade to 1.0.19-8

Code:

pi@raspberrypi:~ $ apt-cache policy fr24feed
fr24feed:
  [COLOR="#FF0000"]Installed: 1.0.19-8[/COLOR]
  Candidate: 1.0.19-8
............

Code:

pi@raspberrypi:~ $ 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 [COLOR="#FF0000"][B]fr24:fr24[/B][/COLOR] /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt
ExecStartPre=-/bin/chmod a+rwx /run/dump1090-mutability
ExecStart=/usr/bin/fr24feed
[COLOR="#FF0000"][B]User=fr24[/B][/COLOR]
[COLOR="#FF0000"][B]Group=fr24[/B][/COLOR]
PermissionsStartOnly=true
StandardOutput=null

[Install]
WantedBy=multi-user.target

**mgunther** · 2018-01-25, 18:59

Updated to 1.0.19-8. No issues so far, all is working well.

One observation: Not sure at what version the following line was added to /etc/systemd/system/fr24feed.service:

Code:

ExecStartPre=-/bin/chmod a+rwx /run/dump1090-mutability

I think this mitigates the issues seen earlier when user 'nobody' was set on the directory and dump1090 map and performance graphs were impacted. Now every user can write to this directory so the actual ownership is not a practical issue anymore. Of course, some purists may not agree with those settings but for the average user they are probably OK.

**hazchem** · 2018-01-25, 19:14

Hi just updated to 1.0.19-8 on raspberry pi working fine no problems

**abcd567** · 2018-01-25, 20:06

Updated to 1.0.19-8 on CHIP/Jessie

1. Checked status befre starting upgrading

Code:

chip@chip:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
...................

chip@chip:~$ apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.19-6
  Candidate: 1.0.19-6
......................

chip@chip:~$ apt-cache policy dump1090-fa
dump1090-fa:
  Installed: 3.5.3
  Candidate: 3.5.3

2. Started upgrading

Code:

chip@chip:~$ sudo apt-get update

chip@chip:~$ apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.19-6
  Candidate: 1.0.19-8
...........

chip@chip:~$ sudo /usr/lib/fr24/fr24feed_updater.sh
[COLOR="#FF0000"]/usr/lib/fr24/fr24feed_updater.sh: line 8: ubi0:rootfs: command not found[/COLOR]
............
............
Unpacking fr24feed (1.0.19-8) over (1.0.19-6) ...
Setting up fr24feed (1.0.19-8) ...

Configuration file '/etc/fr24feed.ini'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
 ==> Keeping old config file as default.

Configuration file '/etc/cron.d/fr24feed_updater'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
 ==> Keeping old config file as default.
You don't seem to have any dump1090 installed. On the fr24feed start it will automatically install dump1090-mutability.
Created symlink from /etc/systemd/system/multi-user.target.wants/fr24feed.service to /etc/systemd/system/fr24feed.service.
mount: / is busy

3. Checked after upgrading

FR24 1.0.19-8 on Jessie - Status.png FR24 1.0.19-8 on Jessie - Map.png FR24 1.0.19-8 on Jessie - Graphs.png

Code:

chip@chip:~$ apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.19-8
  Candidate: 1.0.19-8
...................

chip@chip:~$ fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2018-01-25 19:48:05.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-CYYZ30.
[ ok ] FR24 Tracked AC: 24.
[ ok ] Receiver: connected (19498 MSGS/0 SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 23.

Code:

chip@chip:~$ 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 fr24:fr24 /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt
ExecStartPre=-/bin/chmod a+rwx /run/dump1090-mutability
ExecStart=/usr/bin/fr24feed
User=fr24
Group=fr24
PermissionsStartOnly=true
StandardOutput=null

[Install]
WantedBy=multi-user.target

**JohnSunnyhills** · 2018-01-25, 20:39

I can report that I upgraded to 1.0.19-8 this morning on jessie, and my Beast is running in a service ok.
I suspect that this version is still rough around the edges as FR24feed no longer ran when I tried to do it without the service.

So both my RP24s are now running (the DVBT on the earlier version).

For the future, speaking as a semi techo savve, but not in the same level as the majority of gurus who frequent this forum,

It would be great if all the investigative commands that have been tossed around here in the last fewdays could be listed for the future on this site somewhere just so it is possible for feeders to feel their way around their systems.
I am not talking about commands to change permissions etc, just listing logs and versions etc.
Unless I am missing something the documentation available is sparse. :-)

**abcd567** · 2018-01-26, 04:00

@Oblivian
@vi1nnyspb

If on Raspbian, fr24feed is installed first, it will also install dump1090-mutability v 1.14. The Pi24 image is also same.

If subsequently someone installs dump1090-fa also, then at boot would both versions of dump1090 start and compete to grab the DVB-T dongle? If yes then which one will win?

Any ideas?

**ylis** · 2018-01-26, 04:51

I've been trying to create a fresh 1.0.19-8 installation as follows:

Pi24 image - 1.0.18-9

sudo apt-get update

sudo apt install fr24feed

You don't seem to have any dump1090 installed. On the fr24feed start it will automatically install dump1090-mutability.

sudo service fr24feed start

root@raspberrypi:/etc# fr24feed-status

[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2018-01-26 04:43:29.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-YBKE1.
[ ok ] FR24 Tracked AC:.
[FAIL] Receiver: down ... failed!
[FAIL] FR24 MLAT: not running ... failed!

root@raspberrypi:/etc# sudo fr24feed start

2018-01-26 04:29:47 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
2018-01-26 04:29:47 | [reader][e]Could not connect to avr-tcp://127.0.0.1:30002
Repeatedly

Checking the policies
root@raspberrypi:/etc# sudo apt-cache policy fr24feed

fr24feed:
Installed: 1.0.19-8
Candidate: 1.0.19-8
Version table:
*** 1.0.19-8 0
500 http://repo.feed.flightradar24.com/ flightradar24/raspberrypi-stable armhf Packages
100 /var/lib/dpkg/status

root@raspberrypi:/etc# sudo apt-cache policy dump1090-mutability

N: Unable to locate package dump1090-mutability

root@raspberrypi:/etc# sudo apt-cache policy dump1090-fa

N: Unable to locate package dump1090-fa

root@raspberrypi:/etc# sudo apt-cache policy dump1090

N: Unable to locate package dump1090

If fr24feed starts first then installs dump1090-mutability ... it doesn't seem to install dump1090 if the AVR stick isn't connected - and to connect, it seems to need dump1090 installed. Or have I got this all wrong ??

What is the preferred sequence and order of commands to create a new blank plain and simple installation ?

Thanks

Peter

**abcd567** · 2018-01-26, 05:05

Try
sudo reboot

Then check

fr24feed-status

apt-cache policy dump1090-mutability

**abcd567** · 2018-01-26, 06:10

Originally posted by Oblivian

There's a d1090 install .sh somewhere that crudely for dvbt and if it's there tows down d1090 and applies. Can't recall exact location, few posts back.

First make sure setting is "DVBT" (installation script will proceed only if grep -q "^receiver.*dvbt" /etc/fr24feed.ini)
cd /usr/lib/fr24/
sudo ./install_dump1090.sh

**YoshiH** · 2018-01-26, 11:47

Originally posted by vinnyspb

you seem to have something weird with dirmgnr, try

Tried it and updated to 1.0.19-8 and stil "mlat_problem="no-config"

Code:

ac_map_size="3072"
build_arch="static_arm"
build_flavour="generic"
build_os="Linux"
build_revision="HEAD-dc09ce0.git"
build_timetamp="Jan 25 2018 14:01:58"
build_version="1.0.19-8"
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="1516966925"
feed_last_config_attempt="1516966924"
feed_last_config_info=""
feed_last_config_result="success"
feed_last_connected_time="1516966925"
feed_status="connected"
feed_status_message=""
fr24key="I_REMOVED_MY_KEY"
last_json_utc="1516966887"
last_rx_connect_status="OK"
last_rx_connect_time="1516966946"
last_rx_connect_time_s="2018-01-26 11:42:26"
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="1516966932"
time_update_utc_s="2018-01-26 11:42:12"
timing_is_valid="1"
timing_last_drift="-0.0000"
timing_last_offset="-0.0000"
timing_last_result="success"
timing_source="NTP"
timing_time_last_attempt="1516966924"
timing_time_last_success="1516966924"
timing_time_since_last_success="1516966924"

Code:

Linux/generic/static_arm/1.0.19-8

Updated: 12:47:46 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

Announcement

Archived: Feed issues with 19-2

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment