Archived: Feed issues with 19-2

[equi]

tl;dr Since the Update the Feeder does not upload aircrafts from my 2nd Installation.

I have two ADS-B Feeder (dump1090 muta installation), on the RPi there are two dump1090 instances running. An instance to grab the ADS-B signal from the stick and the 2nd instance is an ADS-B Hub. On this hub, the Banana Pi (2nd Feeder) and the first instance submit it's ADS-B data so they merge it. The FR24 grabs from the hub and sends data to the FR24-Servers. Before 1.0.19-8 the feeder included the Banana Pi ADS-B Data so I uploaded more, but since the update it discards the Banana Pi ADS-B Data for some reason. My VRS Installation does this not, so the hub is running fine.

[JulHer]

I need help... Raspbian Jessie

$ apt-cache policy fr24feed
fr24feed:
Instalados: 1.0.19-8
Candidato: 1.0.19-8
Tabla de versión:
*** 1.0.19-8 0
500 http: repo.feed.flightradar24.com/ flightradar24/raspberrypi-stable armhf Packages
100 /var/lib/dpkg/status

$ apt-cache policy dump1090-mutability
dump1090-mutability:
Instalados: 1.14
Candidato: 1.14
Tabla de versión:
*** 1.14 0
100 /var/lib/dpkg/status

$ apt-cache policy dump1090
N: No se ha podido localizar el paquete dump1090


$ fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp:.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-LEVX17.
[ ok ] FR24 Tracked AC:.
[FAIL] Receiver: down ... failed!
[FAIL] FR24 MLAT: not running ... failed!

$ dpkg -l|grep dump
iHR dump1090-mutability 1.14 armhf

$ cat /etc/fr24feed.ini
receiver="dvbt"
fr24key="...Key_ID..."
path="/usr/lib/fr24/dump1090"
bs="no"
raw="no"
logmode="1"
procargs="--net --net-http-port 8888"
mlat="no"
mlat-without-gps="no"


$cat fr24feed.log

2018-01-28 18:43:03 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 8888 --raw)
2018-01-28 18:43:03 | [reader][i]Connected to the receiver, configuring
2018-01-28 18:43:03 | [reader][i]Configured, processing messages
2018-01-28 18:43:03 | [reader][i]Connection terminated
2018-01-28 18:43:03 | [main][i]Terminating child process 1884 with SIGTERM
2018-01-28 18:43:08 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 8888 --raw)
2018-01-28 18:43:08 | [reader][i]Connected to the receiver, configuring
2018-01-28 18:43:08 | [reader][i]Configured, processing messages
2018-01-28 18:43:08 | [reader][i]Connection terminated
2018-01-28 18:43:08 | [main][i]Terminating child process 1885 with SIGTERM
2018-01-28 18:43:11 | [main][i]Terminating on user request
2018-01-28 18:43:11 | [main][i]Terminating worker threads
2018-01-28 18:43:11 | [reader][i]Terminating on request
2018-01-28 18:43:12 | [master][i]Terminating on request
2018-01-28 18:43:12 | [feed][n]busy
2018-01-28 18:43:12 | [feed][n]disconnected
2018-01-28 18:43:12 | [feed][x]Feeding thread terminated

My radar is not working...

[abcd567]

@JulHer

For restart/connection terminated run the command 3 posts back for blacklist rtl device and reboot again.

I think Oblivian refers to this:

sudo wget -O  /etc/udev/rules.d/rtl-sdr.rules "https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules"

sudo reboot

fr24feed-status

[JulHer]

@JulHer



I think Oblivian refers to this:

sudo wget -O  /etc/udev/rules.d/rtl-sdr.rules "https: raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules"

sudo reboot

fr24feed-status

Is that necessary also for Jessie?

[abcd567]

FINGERS CROSSED
Created a custom install with ver 1.0.18-9.
Waiting for auto-uppdate to ver 1.0.19-8.
Fingers Crossed

FR24 Map - replicate custom install with ver 1.0.18-9.png FR24 Status - replicate custom install with ver 1.0.18-9.png FR24 Settings - replicate custom install with ver 1.0.18-9.png FR24 Graphs ver 1.0.18-9 on Jessie.jpg

DETAILS
(A) Burned microSD card with "2017-07-05-raspbian-jessie-lite" image (Click Here to Download from Raspberrypi.org Archives).

(B) Manually installed dump1090-mutability ver 1.14 AND fr24feed ver 1.0.18-9 as follows

1. Updated and installed dependencies
   

   ~ $ sudo apt-get update 
   ~ $ sudo apt-get install librtlsdr0
   ~ $ sudo apt-get install dirmngr

2. Installed dump1090-mutability ver 1.14
   

   ~ $ wget https://github.com/mutability/dump1090/releases/download/v1.14/dump1090-mutability_1.14_armhf.deb
   ~ $ sudo dpkg -i dump1090-mutability_1.14_armhf.deb

3. Installed lighttpd web server
   

   ~ $ sudo apt-get install lighttpd
   ~ $ sudo lighty-enable-mod dump1090
   ~ $ sudo /etc/init.d/lighttpd force-reload

4. Configured dump1090-mutability
   

   ~ $ sudo dpkg-reconfigure dump1090-mutability 
   
   #Set YES to start dump1090-mutability automatically at boot
   #Added Latitude and Longitude info in dump1090-mutability
   
   #To accept MLAT results feed-back from Flightaware, 
   #added "--net-bi-port 30104" (without quotes), 
   #in the field "Extra arguments to pass to dump1090"
   
   #Accepted ALL OTHER default settings presented during reconfigure by pressing Enter key

5. Installed fr24feed ver 1.0.18-9
   

   ~ $ sudo wget http://repo.feed.flightradar24.com/rpi_binaries/fr24feed_1.0.18-9_armhf.deb
   ~ $ sudo dpkg -i fr24feed_1.0.18-9_armhf.deb

6. Made fr24 feeder settings
   Skipped signup process
   Directly entered fr24key and receiver & host info in file fr24feed.ini
   

   ~ $ sudo nano /etc/fr24feed.ini 
   #Added first 3 lines
   
   receiver="avr-tcp"
   host="127.0.0.1:30002"
   fr24key="..CENSORED.."
   
   bs="no"
   raw="no"
   mlat="yes"
   mlat-without-gps="yes"
   
   #Saved (Ctrl+o) and Closed (Ctrl+x)

7. CHECKS
   

   ~ $ ls /usr/lib/fr24
   dump1090             librtlsdr.so    librtlsdr.so.0.5git
   fr24feed_updater.sh  librtlsdr.so.0  public_html
   
   
   ~ $ apt-cache policy fr24feed
   fr24feed:
     Installed: 1.0.18-9
     Candidate: 1.0.18-9
   
   
   ~ $ apt-cache policy dump1090-mutability
   dump1090-mutability:
     Installed: 1.14
     Candidate: 1.14
   
   ~ $ fr24feed-status
   -bash: fr24feed-status: command not found
   
   ~ $ service fr24feed status
   ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
      Loaded: loaded (/etc/init.d/fr24feed)
      Active: [color=#00AA00]active (running)[/color] since Sun 2018-01-28 05:20:12 EST; 9h ago
     Process: 617 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
      CGroup: /system.slice/fr24feed.service
              └─666 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt --write-pid=/var/run/fr24feed.pid --quiet --log-base=/var/log/fr24feed --log-r...

   Contents of dump1090-mutability's html folder
   

   ~ $ ls /usr/share/dump1090-mutability/html
   config.js  coolclock  gmap.html  planeObject.js  script.js  spinny.gif  style.css

   Locations of dump1090-mutability related files/folders
   

   ~ $ sudo find / -name dump1090-mutability
   /etc/default/dump1090-mutability
   /etc/logrotate.d/dump1090-mutability
   /etc/init.d/dump1090-mutability
   /usr/share/dump1090-mutability
   /usr/share/doc/dump1090-mutability
   /usr/bin/dump1090-mutability
   /run/dump1090-mutability

   Locations of file fr24feed.service
   

   ~ $ sudo find / -name fr24feed.service
   /etc/systemd/system/multi-user.target.wants/fr24feed.service
   /sys/fs/cgroup/systemd/system.slice/fr24feed.service
   /run/systemd/generator.late/fr24feed.service
   /run/systemd/generator.late/runlevel5.target.wants/fr24feed.service
   /run/systemd/generator.late/runlevel4.target.wants/fr24feed.service
   /run/systemd/generator.late/runlevel3.target.wants/fr24feed.service
   /run/systemd/generator.late/runlevel2.target.wants/fr24feed.service

8. ADDITIONAL SOFTWARE INSTALLED
   • Performance Graphs (rrdtools/collectd)
   • FlightAware data feeder
   • Planefinder data feeder
   • Radarbox24 data feeder
   • Adsbexchange datafeeder
   
   

[Guest]

We've finally managed to reproduce the issue which prevented original updates from 1.0.18-9 for some of the feeders.

It is fixed in version 1.0.19-11 which is currently published to beta channel in APT and I'm going to promote it to stable in a few hours.

[abcd567]

FINGERS CROSSED
Created a custom install with ver 1.0.18-9.
Waiting for auto-uppdate to ver 1.0.19-8.
Fingers Crossed

Even after waiting for 36 hrs, automatic update did not take place.

Realized that I have installed fr24feed 1.0.18-9 by getting .deb package directly from repo.feed.flightradar24.com using wget command, and the apt keys are not installed. As a result "apt-cache policy fr24feed" showed both Installed and candidate as 1.0.18-9. Even runnig "sudo apt-get update" and then checking again gave same result.

I now installed gpg keys as follows (had to switch to user root to get it done)

#Added password of my choice to user root
pi@raspberrypi:~ $ sudo passwd root
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully

#Switched from user pi to user root, using new root password whichwas set as above.
pi@raspberrypi:~ $ su root
Password:

#Started manual install of gpg key
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

#Switvhed back to user pi
root@raspberrypi:/home/pi# su pi

#Updated apt
pi@raspberrypi:~ $ sudo apt-get update

Now showing "Candidate 1.0.19-11".
Expecting auto-update within next 24 hrs.

pi@raspberrypi:~ $ sudo apt-get update

pi@raspberrypi:~ $ apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.18-9
  [Color=#ff0000]Candidate: 1.0.19-11[/color]
..........

[equi]

Found the issue for my problem, the feeder keeps connecting to the wrong port.

from my fr24feed.ini

host="127.0.0.1:30008

<thats the correct Port, now the magic begins

2018-01-29 18:29:48 | [reader][i]Initializing reader
2018-01-29 18:29:48 | [mlat][i]Waiting for MLAT configuration
2018-01-29 18:29:48 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:[B]30005[/B])
2018-01-29 18:29:48 | [reader][i]Connected to the receiver, configuring
2018-01-29 18:29:48 | [reader][i]Configured, processing messages

It looks like that the Port is hard coded somewhere in the Feeder, it would be nice if the Devs can fix that - asap!

Version is 1.0.19-11

[jrf]

Successful upgrade from 1.0.19-6 to 1.0.19-11 on RPI applying no additional changes.

sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot now

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

[Oblivian]

Killer question is, was it broken on -6 and did -11 fix

Sent from my XT1092 using Tapatalk

[jrf]

It was running on -6 after changing the user in the fr24feed.service to root. User mgunthers post helped me on that. Now I didn't do any changes for the upgrade to -11.

[abcd567]

@jrf
Can you please check file fr24feed.service and see if after upgrade from 19-6 to19-11, did you change of user:root is still there oris it now user:fr24?

[Oblivian]

Bit of useless info.

All started after 19-2 release. All various reported, but related to ongoing changes

Either heavy handed removed due to mid-version change. Or due to duplicate/resolved issue and or now misleading/old fix info that doesn't need to confuse people more

FR1.jpgFR2.JPG

Excluding individual post moved or deleted that were added to older threads after keywords were searched from seen errors, such as MLAT, feed, offline and so on and then posted on the end of.

[thehague]

Updated from 1.0.19-8 to 1.0.19-11. Finally I don't have to change the user in fr24feed.service anymore. It's running fine with fr24:fr24.

[jrf]

@jrf
Can you please check file fr24feed.service and see if after upgrade from 19-6 to19-11, did you change of user:root is still there oris it now user:fr24?

It is now fr24:fr24. I posted the success because I wanted to encourage others that did some manually fiddling like me to update.