AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: Radarbox connected for 3 days, then disconnected AGAIN  (Read 1029 times)

0 Members and 1 Guest are viewing this topic.

abcd567

  • Hero Member
  • *****
  • Posts: 674
  • CYYZ - Toronto
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #15 on: August 20, 2022, 01:24:22 AM »
@Av8tor_from_Argentina:
Please REBOOT your Pi then check again


Please also see this thread
https://forum.radarbox24.com/index.php?topic=106461
« Last Edit: August 20, 2022, 01:25:55 AM by abcd567 »

Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #16 on: August 20, 2022, 03:08:00 PM »
Something is not right here,


[client]
network_mode=true
log_file=/var/log/rbfeeder.log

key=xxxxxxxx

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

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


As you can see there is no REFERENCE to Station Name or even LAT/LONG data...

Is there any way of reset and execute the setup in a way of ENTER all data again?, because everytime that I´ve executed the installer, never asked for position, altitude and email... And clearly remember that setup asked for that kind of information.

...

abcd567

  • Hero Member
  • *****
  • Posts: 674
  • CYYZ - Toronto
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #17 on: August 20, 2022, 04:23:39 PM »
Something is not right here,


[client]
network_mode=true
log_file=/var/log/rbfeeder.log

key=xxxxxxxx

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

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


As you can see there is no REFERENCE to Station Name or even LAT/LONG data...

Is there any way of reset and execute the setup in a way of ENTER all data again?, because everytime that I´ve executed the installer, never asked for position, altitude and email... And clearly remember that setup asked for that kind of information.

...

(1) Did you REBOOT your Pi? If yes, then did following error messsge disappear from status output?

Code: [Select]
failed to rename /dev/shm//rbfeeder_receiver.json.2coDHx to /dev/shm//rbfeeder_receiver.json: Operation >


(2) Did you add your key by following command or was it there automatically?
Code: [Select]
sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

(3) Once you have the key, and enter it by above command, the setup wont ask for email. It asks for email only when you dont enter a key and go to claims page to claim a new station.

(4) Location data (latitude, longitude, and altitude above sea level in meters) can be entered manually by you in the rbfeeder.ini file just above [network], and save the file. See below my file

(5) The station number "sn=EXTRPIxxxxxx" automatically gets entered when your key is accepted. You dont have to enter station number yourself. Are you sure the key you are using is correct and complete? Count that all 32 characters are there, no chrecters are left out in copy-pasting.



Quote

[email protected]:~ $ sudo nano /etc/rbfeeder.ini

[client]
network_mode=true
log_file=/var/log/rbfeeder.log
disable_log=1

key=xxxxxxxxxxxxxxxxxxxxxxx
sn=EXTRPI000008

lat=43.5xxxxx
lon=-79.6xxxxx
alt=1xx


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

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


« Last Edit: August 20, 2022, 04:32:36 PM by abcd567 »

Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #18 on: August 20, 2022, 05:55:23 PM »
Well seems that, Radarbox universe is against one more time...

Purge, removed, deleted every trace of rbfeeder...

Installed again, stopped, rebooted pi and status again...

Attached file with results


Is there any way to start with a new key? I left it worked for 30 minutes without a key and it has never created a new one. Also requested to radarbox support to check my current key with station name and is OK, KEY match with station....

Want to create a new account but how can I do that ??

I will become a Tibetan Buddhist monk...

abcd567

  • Hero Member
  • *****
  • Posts: 674
  • CYYZ - Toronto
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #19 on: August 20, 2022, 09:23:01 PM »
Well seems that, Radarbox universe is against one more time...

Purge, removed, deleted every trace of rbfeeder...

Installed again, stopped, rebooted pi and status again...

Attached file with results


From your attached file:
Code: [Select]
Aug 20 14:43:19 raspberry rbfeeder[529]: getaddrinfo: Temporary failure in name resolution
Aug 20 14:43:19 raspberry rbfeeder[529]: [2022-08-20 14:43:19]  Can't connect to AirNav Server.

OK I think following will solve the above noted issue of connectivity to AirNav Server:

Code: [Select]
sudo apt update

sudo apt install netbase   

sudo reboot 

After reboot check
(a) rbfeeder's status
(b) file rbfeeder.ini

Hope your multiple-disease iinstall (mutiple versions saved in apt-cache, broken/corrupted rbfeeder package, missing netbase package) will be solved finally.
.
« Last Edit: August 20, 2022, 09:38:06 PM by abcd567 »

Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #20 on: August 21, 2022, 09:29:43 PM »
Hello there.... performed AGAIN  STOP, PURGE, reinstall, netbase, restart...
Nothing...
So I will let Radarbox set a new key for me...
this is what rbfeeder.ini looks now...

[client]
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
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true


Also a search for a key...

[email protected]:~ $ sudo rbfeeder --showkey

Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.
Configuration file: /etc/rbfeeder.ini


[email protected]:~ $ less /var/log/rbfeeder.log
[2022-08-21 18:34:17]  Data sent: 250 B
[2022-08-21 18:34:17]  Data received: 0 B
[2022-08-21 18:35:02]  Connection established.
[2022-08-21 18:35:02]  Empty sharing key. We will try to create a new one for you!
[2022-08-21 18:35:12]  Timeout waiting for new key. Will try again in 30 seconds.
[2022-08-21 18:35:19]  ******** Statistics updated every 60 seconds ********
[2022-08-21 18:35:19]  Packets sent in the last 60 seconds: 1, Total packets sent since startup: 11
[2022-08-21 18:35:19]  Data sent: 275 B
[2022-08-21 18:35:19]  Data received: 0 B
[2022-08-21 18:36:13]  Connection established.
[2022-08-21 18:36:13]  Empty sharing key. We will try to create a new one for you!
[2022-08-21 18:36:19]  ******** Statistics updated every 60 seconds ********
[2022-08-21 18:36:19]  Packets sent in the last 60 seconds: 1, Total packets sent since startup: 12
[2022-08-21 18:36:19]  Data sent: 300 B
[2022-08-21 18:36:19]  Data received: 0 B
[2022-08-21 18:36:24]  Timeout waiting for new key. Will try again in 30 seconds.
[2022-08-21 18:36:31]  Starting RBFeeder Version 1.0.8 (build 20220708190411)
[2022-08-21 18:36:31]  Using configuration file: /etc/rbfeeder.ini
[2022-08-21 18:36:31]  Network-mode enabled.
[2022-08-21 18:36:31]           Remote host to fetch data: 127.0.0.1
[2022-08-21 18:36:31]           Remote port: 30005
[2022-08-21 18:36:31]           Remote protocol: BEAST
[2022-08-21 18:36:31]  Using GNSS (when available)


[email protected]:~ $ sudo systemctl status rbfeeder
● rbfeeder.service - RBFeeder Service
     Loaded: loaded (/lib/systemd/system/rbfeeder.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-08-21 18:23:07 -03; 15min ago
    Process: 1632 ExecStartPre=/bin/mkdir /var/run/rbfeeder (code=exited, status=1/FAILURE)
    Process: 1633 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/run/rbfeeder (code=exited, status=0/SUCCESS)
    Process: 1634 ExecStartPre=/bin/touch /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
    Process: 1635 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
    Process: 1636 ExecStartPre=/bin/chown rbfeeder:rbfeeder /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
    Process: 1637 ExecStartPre=/bin/setfacl -m u:www-data:rwx /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
   Main PID: 1638 (rbfeeder)
      Tasks: 9 (limit: 1597)
        CPU: 4.360s
     CGroup: /system.slice/rbfeeder.service
             └─1638 /usr/bin/rbfeeder

Aug 21 18:37:25 raspberry rbfeeder[1638]: [2022-08-21 18:37:25]  Connection established.
Aug 21 18:37:25 raspberry rbfeeder[1638]: [2022-08-21 18:37:25]  Empty sharing key. We will try to create a new one for you!
Aug 21 18:37:35 raspberry rbfeeder[1638]: [2022-08-21 18:37:35]  Timeout waiting for new key. Will try again in 30 seconds.
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  ******** Statistics updated every 60 seconds ********
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  Packets sent in the last 60 seconds: 1, Total packets sent since startup: 13
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  Data sent: 325 B
Aug 21 18:38:22 raspberry rbfeeder[1638]: [2022-08-21 18:38:22]  Data received: 0 B
Aug 21 18:38:36 raspberry rbfeeder[1638]: [2022-08-21 18:38:36]  Connection established.


No key, no coordinates, no station name... NOTHING...

That´s why I am asking if it is any command that can perform a setup like the FIRST TIME EVER... The kind of setup that a newby or someone who has never ever installed Radarbox24 software....

It´s a truly dissapointing experience....
« Last Edit: August 21, 2022, 09:39:57 PM by Av8tor_from_Argentina »

abcd567

  • Hero Member
  • *****
  • Posts: 674
  • CYYZ - Toronto
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #21 on: August 22, 2022, 01:36:50 AM »
@Av8tor_from_Argentina

Your software setup has become ok after purging and deleting old ones and installing new copy. Also after installing package netbase, you should not have any problem in connecting to AirNav Servers.

However as your latest logs show, rbfeeder is unable to obtain key from AirNav Server, and keeps on trying. This shows connection issue.

The possible reasons are Firewall settings in your router or local network. Has your router been recently changed by your internet service provider?

Another reason of failure to connect is to use IPv6 instead of IPv4. I have very little knowledge about Firewalls and IPv6. Better contact your internet service provider and tell them that your Pi is unable to connect to AirNav server through their Router. They may change settings of your router to allow connection.

Dennis_K

  • New Member
  • *
  • Posts: 2
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #22 on: August 22, 2022, 10:57:51 AM »
Having a similar issue since yesterday, the connection is working fine for a while but will break eventually.
Log shows the following when the connection breaks:
Code: [Select]
******** Statistics updated every 60 seconds ********
Packets sent in the last 60 seconds: 0, Total packets sent since startup: 2
Data sent: 126 B
Data received: 0 B
Connection established.
Could not start connection. Timeout.

I did some troubleshooting and noticed the following the moment the timeout occurs:
TCP handshake with rpiserver-ng.rb24.com is successful. RBFeeder now sends a small package
Code: [Select]
Internet Protocol Version 4, Src: 172.17.0.5, Dst: rpiserver-ng.rb24.com (23.29.123.254)
Transmission Control Protocol, Src Port: 55528, Dst Port: 33755, Seq: 1, Ack: 1, Len: 2
Source Port: 55528
Destination Port: 33755
[Stream index: 13]
[Conversation completeness: Incomplete, DATA (15)]
[TCP Segment Len: 2]
Sequence Number: 1 (relative sequence number)
Sequence Number (raw): 1368053075
[Next Sequence Number: 3 (relative sequence number)]
Acknowledgment Number: 1 (relative ack number)
Acknowledgment number (raw): 442404819
1000 .... = Header Length: 32 bytes (8)
Flags: 0x018 (PSH, ACK)
Window: 502
[Calculated window size: 64256]
[Window size scaling factor: 128]
Checksum: 0xaa54 [unverified]
[Checksum Status: Unverified]
Urgent Pointer: 0
Options: (12 bytes), No-Operation (NOP), No-Operation (NOP), Timestamps
[Timestamps]
[SEQ/ACK analysis]
TCP payload (2 bytes)
Data (2 bytes)
Data: 7e23
[Length: 2]
and rpiserver-ng.rb24.com is closing the connection (fin+rst).
When the connection is working, rpiserver-ng.rb24.com is responding with ACK to the same package and is  keeping the connection alive.

Hard to tell if Av8tor_from_Argentina is having the exact same issue, but the symptoms are the same
« Last Edit: August 22, 2022, 11:00:42 AM by Dennis_K »

Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #23 on: August 22, 2022, 11:05:26 AM »
Is there any remote possibility that dump 1090 (mutability or fa) is failing? how can I know which Dump1090 I have installed and running? Which one is recommended? Remember that I have FR24, Flightaware and PlaneFinder working PERFECT...

I would guess that I have Mutability, because I can see a map with Skyaware...
« Last Edit: August 22, 2022, 11:07:34 AM by Av8tor_from_Argentina »

abcd567

  • Hero Member
  • *****
  • Posts: 674
  • CYYZ - Toronto
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #24 on: August 22, 2022, 11:24:41 AM »
Is there any remote possibility that dump 1090 (mutability or fa) is failing? how can I know which Dump1090 I have installed and running? Which one is recommended? Remember that I have FR24, Flightaware and PlaneFinder working PERFECT...

I would guess that I have Mutability, because I can see a map with Skyaware...


Output of following command will show which one is installed
Code: [Select]
apt-cache policy dump1090-mutability 

apt-cache policy dump1090-fa 



On my Pi with dump 1090-fa, I get:

[email protected]:~ $ apt-cache policy dump1090-fa
dump1090-fa:
  Installed: 7.2
  Candidate: 7.2
  Version table:
 *** 7.2 500
        500 https://raw.githubusercontent.com/abcd567a/rpi/master ./ Packages
        100 /var/lib/dpkg/status


[email protected]:~ $ apt-cache policy dump1090-mutability
dump1090-mutability:
  Installed: (none)
  Candidate: 1.15~20180310.4a16df3+dfsg-8
  Version table:
     1.15~20180310.4a16df3+dfsg-8 500
        500 http://deb.debian.org/debian bullseye/main arm64 Packages





Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #25 on: August 22, 2022, 09:13:47 PM »
Thanks, I have dump1090-fa.

Will check my repeater (in which raspi is connected) to see if there are a mob of strange gremlins that avoid Radarbox to connect...

From now on, is a matter of personal challenge to connect RB24, cannot understand why is the only flight tracker software that is unable to relay information. And I don´t want to reformat my SD card because FR, FA and PlaneFinder work perfect...

Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #26 on: August 25, 2022, 10:36:41 PM »
There is no firewall problem or port closed... Flightradar, Flightaware and Planefinder work straight with no network or router problems or firewall rules...

I´ve contacted RadarBox support, but would guess that there is no going to be any kind of solution. And the solution will be format and reinstall everything again, which I will not goint to do because I´m not going to reformat and reinstall for just one app...

still open to new ideas...

Av8tor_from_Argentina

  • New Member
  • *
  • Posts: 26
Re: Radarbox connected for 3 days, then disconnected AGAIN
« Reply #27 on: August 25, 2022, 10:39:49 PM »
Having a similar issue since yesterday, the connection is working fine for a while but will break eventually.

Hard to tell if Av8tor_from_Argentina is having the exact same issue, but the symptoms are the same

Dennis, good evening. Any news or solution to your problem?

Regards,