Adding UAT 978 to existing 1090 install

[vantage]

So the rhetorical question now is:

Are they being sent correctly to RB24 as UAT and RB24 are misinterpreting/misdisplaying the source
or
they're being *sent* to RB24 incorrectly even though my station is detecting them as UAT?

I've sent all the info to support with nc command output and screenshots and am waiting to hear back.

[Runway 31]

No idea, however be advised that support personnel are not tech so dont expect an answer that will satisfy you

Alan

[vantage]

I've already gotten to two separate email requests from support:
First: can you send us the last few lines of the log file please.

and then: That does show all is connected, can you send the ini file again please?

I assumed support was the tech people. Apparently they're just a pass-through between the feeders and the tech people.

[Runway 31]

That is correct

Alan

[abcd567]

My diagnosis is that in vantage's rbfeeder installation, some files are broken, corrupted or missing. I formed this opinion because dump978-rb is giving proper output on both ports 30978 and 28380. This was confirmed by
commands  "nc 127.0.0.1 30978"  and "nc 127.0.0.1 28380".

On the other hand rbfeeder, which collects dats from dump978 and dump1090 and passes these to Air Nav Servers complints it cannot connect to port 30978.

In view of above, the best option is to completely purge rbfeeder and all its files, and then install it fresh.

(1) open file /etc/rbfeeder.ini and from it copy-paste key to you PC Notepad and save it.

(2) Give following command to remove rbfeeder

Code: [Select]

sudo apt purge rbfeeder   

sudo reboot 


(3) Make a fresh install of rbfeeder

Code: [Select]

sudo apt update 

sudo apt install rbfeeder 

sudo reboot

(4) After reboot check status

Code: [Select]

sudo systemctl status rbfeeder 



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

[vantage]

I'll keep that in mind... and at some point I would need to copy back the /etc/rbfeeder.ini. Correct?

In the meantime I'm doing this as requested by RB24 support:

Just as a test can you remove the line

dump978_port=30978

Save and restart and wait 1 hour. Check whether the log is complaining if not double check whether UAT is appearing on the website. If that all fails add the line back and restart and let us know and we will investigate on our server regarding the data being sent to us.

[Runway 31]

Looks like it was passed to the tech guys

Alan

[abcd567]

Conratulations, it started working.

[vantage]

Thanks. The support guys had me do this experiment which was *not* the total solution:

Sent: Thursday, March 17, 2022 1:51 PM
Just as a test can you remove the line
 
dump978_port=30978 
 
Save and restart and wait 1 hour. Check whether the log is complaining if not double check whether UAT is appearing on the website. If that all fails add the line back and restart and let us know and we will investigate on our server regarding the data being sent to us.

That alone still resulted in this repeating over & over in /var/log/rbfeeder.log:
[2022-03-17 22:20:36]  Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...


I also had to do this to get  dump978-rb working and stop the "Can't connect" messages above :

Code: [Select]

sudo systemctl restart dump978-rb

For some still unknown reason a reboot/cold start always results in  Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second.... At this point it's just an annoyance.

I'm thinking about documenting all the steps I had to take to get 978 working so  others don't have to go through this.

Thanks to  Alan and abcd567 for the help.

[abcd567]

Thanks. The support guys had me do this experiment which was *not* the total solution:

Sent: Thursday, March 17, 2022 1:51 PM
Just as a test can you remove the line
 
dump978_port=30978 
 
Save and restart and wait 1 hour. Check whether the log is complaining if not double check whether UAT is appearing on the website. If that all fails add the line back and restart and let us know and we will investigate on our server regarding the data being sent to us.

How come you got following line in config file of rbfeeder? I have also installed rbfeeder and added dump978-rb. I dont have this line in my rbfeeder's config file. Did you add it manually yourself?

dump978_port=30978 

That alone still resulted in this repeating over & over in /var/log/rbfeeder.log:
[2022-03-17 22:20:36]  Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...


I also had to do this to get  dump978-rb working and stop the "Can't connect" messages above :

Code: [Select]

sudo systemctl restart dump978-rb

For some still unknown reason a reboot/cold start always results in  Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second.... At this point it's just an annoyance.

Very strange.
Tonight I will reboot and check the behaviour of rbfeeder on my RPi.

I'm thinking about documenting all the steps I had to take to get 978 working so  others don't have to go through this.

I am thinking of finding the root cause and a fix, provided I can recreate your situation on my Pi.

[vantage]

How come you got following line in config file of rbfeeder? I have also installed rbfeeder and added dump978-rb. I dont have this line in my rbfeeder's config file. Did you add it manually yourself?

dump978_port=30978 

Here's why:
From: RadarBox Support
Sent: Sunday, March 13, 2022 11:16 AM
After the dump978_enabled = true please add
dump978_port=XXXXX   
the XXX should be the port you are sharing the UAT data on.

[abcd567]

I feel the rbfeeder has got some corrupt/missing files which is causing this issue. The best solution is to purge rbfeeder (sudo apt purge rbfeeder), then reinstall a fresh copy (sudo apt install rbfeeder).

[vantage]

My diagnosis is that in vantage's rbfeeder installation, some files are broken, corrupted or missing. I formed this opinion because dump978-rb is giving proper output on both ports 30978 and 28380. This was confirmed by
commands  "nc 127.0.0.1 30978"  and "nc 127.0.0.1 28380".

On the other hand rbfeeder, which collects dats from dump978 and dump1090 and passes these to Air Nav Servers complints it cannot connect to port 30978.

In view of above, the best option is to completely purge rbfeeder and all its files, and then install it fresh.

(1) open file /etc/rbfeeder.ini and from it copy-paste key to you PC Notepad and save it.

(2) Give following command to remove rbfeeder

Code: [Select]

sudo apt purge rbfeeder   

sudo reboot 


(3) Make a fresh install of rbfeeder

Code: [Select]

sudo apt update 

sudo apt install rbfeeder 

sudo reboot

(4) After reboot check status

Code: [Select]

sudo systemctl status rbfeeder 



I note that the procedure says copy the /etc/rbfeeder.ini and save it. If I don't put it back in, what's the point  other than having a record of what it used to be? Or is there a step missing?

[abcd567]

I note that the procedure says copy the /etc/rbfeeder.ini and save it. If I don't put it back in, what's the point  other than having a record of what it used to be? Or is there a step missing?

The procedure does NOT say to copy and save the whole rbfeeder.ini file.
It tells to copy-paste only the key from it.

(1) open file /etc/rbfeeder.ini and from it copy-paste key to you PC Notepad and save it.

The key will be required by the installer at the end of installation.

Code: [Select]

sudo rbfeeder --setkey ‹your sharing key›



.