Why does running rbfeedr with piaware results in much higher message rate in skyaware / tar1090?
It’s feeding messages back into dump1090 so they are being counted twice. I’m not sure what causes it exactly but there’s something about the rbfeeder setup that can cause it. Double check for it connecting back to the input port of dump1090 in the rbfeeder config.
Not really seeing much in the rbfeeder.ini
network_mode=true
[network]
mode=beast
external_port=30005
external_host=localhost
[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client
And the S/N, key, lat, long, elevation
I did notice rbfeeder opens ipv4 connection on 30005
rbfeeder running
tcp 0 1252 localhost:30005 localhost:50510 ESTABLISHED
tcp 1252 0 localhost:50510 localhost:30005 ESTABLISHED
tcp6 0 0 localhost:59118 localhost:30005 ESTABLISHED
tcp6 1247 0 localhost:57976 localhost:30005 ESTABLISHED
tcp6 0 1247 localhost:30005 localhost:57976 ESTABLISHED
tcp6 0 0 localhost:30005 localhost:59118 ESTABLISHED
rbfeeder not running
tcp6 0 0 localhost:59118 localhost:30005 ESTABLISHED
tcp6 1250 0 localhost:57976 localhost:30005 ESTABLISHED
tcp6 0 1250 localhost:30005 localhost:57976 ESTABLISHED
tcp6 0 0 localhost:30005 localhost:59118 ESTABLISHED
A possiblity is malfunctioning mlat-client supplied and installed from RB24 repository by command sudo apt install mlat-client
.
To test, uninstall it by command sudo apt purge mlat-client
, then REBOOT Pi and check if the excessive high message rate has normalized.
If you find that removal of the RB24 supplied mlat-client has solved the problem, then do NOT reinstall it by command sudo apt install mlat-client
. Instead build and install it from source-code yourself. It is very easy and takes only few minutes:
sudo apt update
sudo apt install -y git curl build-essential debhelper python3 python3-dev dh-python
git clone https://github.com/mutability/mlat-client.git
cd mlat-client
sudo dpkg-buildpackage -b
cd ../
sudo dpkg -i mlat-client_*.deb
Next put mlat-client built by you on hold, so that it does NOT get replaced by RB24 supplied mlat-client during update/upgrade:
sudo apt-mark hold mlat-client
sudo reboot
What I thought would be a quicker test
I stopped mlat-client
Confirmed it was off Active: inactive (dead) since Sat 2023-12-02 09:47:19 EST; 6min ago
No change in the high message rate
stopped rbfeeder on the the piaware host where I’m seeing the high message count, it drops back to normal.
Installed rbfeeder on another host that’s not running any other adsb apps and pointed it to the piaware host.
Instant jump in messages on the piaware host when I start rbfeeder on the other host.
There’s clearly some output loop going on.
Piaware I believe uses 30005 for host data source?. If rb feeder is opening that too, and spitting mlat results out of if you could expect a similar outcome
Is one of the reasons the likes of fr24 told everyone not to feed them if they do others. As multiple clients can share the same
Time to check the fa cmline and ensure it’s the sole source and switch off some of the rb options.
RB Feeder Running:
RB Feeder Stopped
pi@raspberrypi:~ $ sudo netstat -anp | grep -w LISTEN
tcp 0 0 127.0.0.1:32458 0.0.0.0:* LISTEN 848619/rbfeeder
tcp 0 0 127.0.0.1:32459 0.0.0.0:* LISTEN 848619/rbfeeder
tcp 0 0 127.0.0.1:32457 0.0.0.0:* LISTEN 848619/rbfeeder
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1198/lighttpd
tcp 0 0 0.0.0.0:40104 0.0.0.0:* LISTEN 842/mixer
tcp 0 0 0.0.0.0:40004 0.0.0.0:* LISTEN 842/mixer
tcp 0 0 0.0.0.0:40005 0.0.0.0:* LISTEN 842/mixer
tcp 0 0 0.0.0.0:40001 0.0.0.0:* LISTEN 842/mixer
tcp 0 0 0.0.0.0:40002 0.0.0.0:* LISTEN 842/mixer
tcp 0 0 0.0.0.0:40003 0.0.0.0:* LISTEN 842/mixer
tcp 0 0 127.0.0.1:32004 0.0.0.0:* LISTEN 848619/rbfeeder
tcp 0 0 127.0.0.1:32008 0.0.0.0:* LISTEN 848619/rbfeeder
tcp 0 0 0.0.0.0:30154 0.0.0.0:* LISTEN 644/feed-adsbx
tcp 0 0 0.0.0.0:30169 0.0.0.0:* LISTEN 674/feed-adsbfi
tcp 0 0 0.0.0.0:30104 0.0.0.0:* LISTEN 630/dump1090-fa
tcp 0 0 0.0.0.0:30053 0.0.0.0:* LISTEN 1134/pfclient
tcp 0 0 0.0.0.0:30054 0.0.0.0:* LISTEN 1134/pfclient
tcp 0 0 0.0.0.0:32088 0.0.0.0:* LISTEN 848619/rbfeeder
tcp 0 0 0.0.0.0:30004 0.0.0.0:* LISTEN 630/dump1090-fa
tcp 0 0 0.0.0.0:30005 0.0.0.0:* LISTEN 630/dump1090-fa
tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 630/dump1090-fa
tcp 0 0 0.0.0.0:30003 0.0.0.0:* LISTEN 630/dump1090-fa
tcp 0 0 0.0.0.0:8978 0.0.0.0:* LISTEN 1198/lighttpd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1198/lighttpd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 822/sshd: /usr/sbin
tcp 0 0 0.0.0.0:8585 0.0.0.0:* LISTEN 1198/lighttpd
tcp 0 0 0.0.0.0:8542 0.0.0.0:* LISTEN 1198/lighttpd
tcp 0 0 0.0.0.0:30978 0.0.0.0:* LISTEN 836700/dump978-fa
tcp 0 0 0.0.0.0:30979 0.0.0.0:* LISTEN 836700/dump978-fa
tcp6 0 0 :::40104 :::* LISTEN 842/mixer
tcp6 0 0 :::40004 :::* LISTEN 842/mixer
tcp6 0 0 :::40005 :::* LISTEN 842/mixer
tcp6 0 0 :::40001 :::* LISTEN 842/mixer
tcp6 0 0 :::40002 :::* LISTEN 842/mixer
tcp6 0 0 :::40003 :::* LISTEN 842/mixer
tcp6 0 0 :::30154 :::* LISTEN 644/feed-adsbx
tcp6 0 0 :::30169 :::* LISTEN 674/feed-adsbfi
tcp6 0 0 :::30104 :::* LISTEN 630/dump1090-fa
tcp6 0 0 :::30105 :::* LISTEN 6480/fa-mlat-client
tcp6 0 0 :::30106 :::* LISTEN 6480/fa-mlat-client
tcp6 0 0 :::30004 :::* LISTEN 630/dump1090-fa
tcp6 0 0 :::30005 :::* LISTEN 630/dump1090-fa
tcp6 0 0 :::30002 :::* LISTEN 630/dump1090-fa
tcp6 0 0 :::30003 :::* LISTEN 630/dump1090-fa
tcp6 0 0 :::8754 :::* LISTEN 1113/fr24feed
tcp6 0 0 :::80 :::* LISTEN 1198/lighttpd
tcp6 0 0 :::22 :::* LISTEN 822/sshd: /usr/sbin
tcp6 0 0 :::31009 :::* LISTEN 680/python3
tcp6 0 0 :::30978 :::* LISTEN 836700/dump978-fa
tcp6 0 0 :::30979 :::* LISTEN 836700/dump978-fa
tcp6 0 0 :::31003 :::* LISTEN 646/python3
pi@raspberrypi:~ $ sudo systemctl stop rbfeeder
pi@raspberrypi:~ $
Perhaps it is requesting Mode A/C data?
Bingo.
That lead me to this thread - Dump1090 - Message rate too high in Skyaware - #32 by wiedehopf
Confirmed mode a/c messages with jq < /run/dump1090-fa/stats.json ‘.total.local’
disabled mode a/c in piaware-config.txt allow-modeac no
restarted dump1090-fa and rbfeeder, no more high message rate in skyaware/tar1090
For package install of dump1090-fa added EXTRA_OPTIONS=“–no-modeac-auto”
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.