Issue: Problem fetching data from dump1090

[apeiron69]

I know it's million times you find this issue but I would like you to help me. I'm running dump1090 on a raspberry PI and the raspberry feeds to FR24 and to radarbox servers. While radarbox feeding works great, on dump1090 I have since wednesday this message: Problem fetching data from dump1090 AJAX call failed (error: Not Found). Maybe dump1090 is no longer running? The displayed map data will be out of date.and other things you know.
My son, who installed both sistems on raspberry, thinks it is necessary to format and reinstall everything. So I'm asking you: what can I do to check if there (as example) is a single file problem on dump1090 and solve the problem without reintalling everything?

Thanks folks

[abcd567]

(1)Which version of dump1090you are running?
dump1090 Malcolm Robb
dump1090-mutability
dump1090-fa


(2) What are the outputs of following 5 commands?
Note: While posting, remove feeder keys from output of last two commands.


apt policy dump1090


apt policy dump1090-mutability


apt policy dump1090-fa


cat /etc/fr24feed.ini


cat /etc/rbfeeder.ini

[apeiron69]

Thanks for the answer, I'm running dump1090-mutability, 'cause i'm using the FR24 distro.

1)apt policy dump1090:

dump1090:
Installed: (none)
Candidate: (none)
Version table:

---------------------------------------------------

2)apt policy dump1090-mutability:

dump1090-mutability:
Installed: 1.14
Candidate: 1.14
Version table:
*** 1.14 100
100 /var/lib/dpkg/status

-----------------------------------------------------------

3) apt policy dump1090-fa:

N: Unable to locate package dump1090-fa

---------------------------------------------------------

4) cat /etc/fr24feed.ini:


receiver="dvbt"
fr24key="{my_key}"
path="/usr/lib/fr24/dump1090"
bs="no"
raw="no"
logmode="1"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"
procargs="--net --net-bo-port 30005"

---------------------------------------------------

5) cat /etc/rbfeeder.ini:


[client]
key={my_key}
sn=EXTRPI008635

------------------------------------------------------

Thanks for the help!

[abcd567]

cat /etc/rbfeeder.ini
Above command should give many more lines in output than you have posted.

The important parts are missing in what you have posted.


This is what I get:

[client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
sn=EXTRPI000nnn

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true

[apeiron69]

I'm sorry but i've nothing else then what i've written to you before (i've chceked also with nano to avoid the possibility that cat was truncating my output...)... So i don't know what i can do for it... What do you think about this?

[abcd567]

Open file /etc/rbfeeder.ini in nano and copy paste these lines below what you already have:

network_mode=true
log_file=/var/log/rbfeeder.log

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true

After copy-paste, your file will be like this:

[client]
key={my_key}
sn=EXTRPI008635
network_mode=true
log_file=/var/log/rbfeeder.log

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=true

Save file (Ctrl+O) and close nano (Ctrl+X)

Reboot Pi
sudo reboot

Wait few minutes, then check status of fr24feed
sudo fr24feed-status

Check status of RB feeder
sudo systemctl status rbfeeder

Check dump1090mutability map
IP-of-Pi:8080

Check RadarBox24 map

https://www.radarbox.com/stations/EXTRPI008635

[apeiron69]

Ok, thanks a lot, now it seems to work properly. I'll check it for a while just to be sure that it will work and it's a not a temporary fix.

[abcd567]

Your range is poor (Max 89nm) and feed is often yellow ("No Data", i.e. no aircraft received by your system during yellow periods).
You need to improve your hardware (antenna location, antenna, length & type of coax, dvb-t dongle, filter, lna, etc, etc)


Sulmona-EXTRPI008635-RB24.png

[apeiron69]

Yup, I was waiting to buy an used antenna from a guy but he sold it and now I'm try to find one without spending over 50 box...

[abcd567]

Try this almost zero cost "Do It Yourself" antenna

QUICK SPIDER - No Soldering, No Connector

EDIT:
You will also need a pigtail to connect this antenna to your dongle. See this post of above thread:

https://forum.flightradar24.com/forum/radar-forums/technical-matters-hardware/10396-quick-spider-no-soldering-no-connector?p=135903#post135903

[apeiron69]

Thank you. I'll try to do it...

[abcd567]

If you are using the magnetic base antenna supplied with DVB-T, you can improve reception by a very simple method: place antenna over a metallic plate or food can.

If the metallic plate or can is made of iron/steel, it will have added advantage of antenna's magnetic base clinging to it, and holding antenna in upright position.

Mag-mountWhip on Food Can and Near Window-1.jpg

Optimized-Whip-on-Plate-1.jpg

[apeiron69]

Thank you. My antenna, as this, is placed on the metallic edge of a roof window. The problem is that the window is 2 meters under the top level and I'm not able to get signals from west. I've already put a new support for the antenna. I'll do it... Thanks

[VerteX]

Hi
please excuse me, but English is not my native language, i don't want create another topic but I have similar problem wich i cant manage myself.
On my raspi on attic I have installed dump mutability, fr feeder, planefinder feeder and flight avare feeder, all works great until about 2 month ago, looks like dump1090 stooping sending data, when I restart all sudo reboot or just dump1090 sudo service dump1090-mutability restart everything start working sometimes few hours sometimes few days ad again stop, all feeders works just don't received any data from dump, I just don't now how to diagnose problem, everything looks ok. :-(, maybe its hardware problem?

pi@raspberrypi:~ $ sudo systemctl status dump1090-mutability -l
● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
Loaded: loaded (/etc/init.d/dump1090-mutability; generated)
Active: active (running) since Tue 2020-06-16 19:45:36 BST; 12min ago
Docs: man:systemd-sysv-generator(8)
Process: 507 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)
Tasks: 3 (limit: 2200)
Memory: 5.2M
CGroup: /system.slice/dump1090-mutability.service
└─528 /usr/bin/dump1090-mutability --net --ppm 0 --fix --lat 52.3 --lon -0.18 --

Jun 16 19:45:34 raspberrypi systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
Jun 16 19:45:36 raspberrypi systemd[1]: Started LSB: dump1090 daemon (mutability variant).
pi@raspberrypi:~ $

pi@raspberrypi:~ $ apt policy dump1090-mutability
dump1090-mutability:
Installed: 1.15~dev
Candidate: 1.15~dev
Version table:
*** 1.15~dev 100
100 /var/lib/dpkg/status
1.15~20180310.4a16df3+dfsg-6 500
500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
pi@raspberrypi:~ $

https://flightaware.com/adsb/stats/user/Valsary#stats-106693

[abcd567]

VerteX:

Such problems are often caused by power supply.
The 5V dc power supply adaptor gone bad or of insufficient capacity. If you are using a phone charger, it is incapble to deliver sufficient power to RPi. Try another power supply, preferably the official one.

If using another better power supply does not solve the problem, then it may be due to bad dongle or bad connectors or bad coax cable. Check these