trying again

Discussion in 'Feeding' started by Dutchyb, Oct 18, 2020.

  1. Dutchyb

    Dutchyb New Member

    Did the extra install.
    Empty cache refreshed the page and still the ugly red face


    sudo journalctl -u adsbexchange-feed --no-pager

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: BeastReduce TCP output: Attempting connection to feed.adsbexchange.com port 30004 ...

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ...

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Connection established: 127.0.0.1 port 30005

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Attempting connection to localhost port 30157 ...

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Connection to localhost (127.0.0.1) port 30157 failed: 111 (Connection refused)

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 30004

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: UUID: 2a4a936c-0198-4db8-8fc6-b441642864d5

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Attempting connection to localhost port 30157 ...

    Oct 18 15:23:33 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Connection to localhost :):1) port 30157 failed: connect: Cannot assign requested address

    Oct 18 15:24:03 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Attempting connection to localhost port 30157 ...

    Oct 18 15:24:03 raspberrypi adsbexchange-feed[31832]: Beast TCP input: Connection established: localhost (127.0.0.1) port 30157

    [email protected]:~ $

    sudo journalctl -u adsbexchange-mlat --no-pager

    Oct 18 15:38:33 raspberrypi adsbexchange-mlat[31848]: Aircraft: 4 of 8 Mode S, 8 of 12 ADS-B used

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Receiver status: connected

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Server status: ready

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Receiver: 110.2 msg/s received 27.2 msg/s processed (25%)

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Server: 0.1 kB/s from server 0.3kB/s TCP to server 0.0kB/s UDP to server

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Results: 84.4 positions/minute

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Aircraft: 5 of 13 Mode S, 9 of 11 ADS-B used

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Receiver status: connected

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Server status: ready

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Receiver: 152.4 msg/s received 38.1 msg/s processed (25%)

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Server: 0.1 kB/s from server 0.4kB/s TCP to server 0.0kB/s UDP to server

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Results: 73.8 positions/minute

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Aircraft: 6 of 12 Mode S, 9 of 13 ADS-B used

    \
    Oct 18 15:38:33 raspberrypi adsbexchange-mlat[31848]: Aircraft: 4 of 8 Mode S, 8 of 12 ADS-B used

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Receiver status: connected

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Server status: ready

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Receiver: 110.2 msg/s received 27.2 msg/s processed (25%)

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Server: 0.1 kB/s from server 0.3kB/s TCP to server 0.0kB/s UDP to server

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Results: 84.4 positions/minute

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Aircraft: 5 of 13 Mode S, 9 of 11 ADS-B used

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Receiver status: connected

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Server status: ready

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Receiver: 152.4 msg/s received 38.1 msg/s processed (25%)

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Server: 0.1 kB/s from server 0.4kB/s TCP to server 0.0kB/s UDP to server

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Results: 73.8 positions/minute

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Aircraft: 6 of 12 Mode S, 9 of 13 ADS-B used
    Oct 18 15:38:33 raspberrypi adsbexchange-mlat[31848]: Aircraft: 4 of 8 Mode S, 8 of 12 ADS-B used

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Receiver status: connected

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Server status: ready

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Receiver: 110.2 msg/s received 27.2 msg/s processed (25%)

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Server: 0.1 kB/s from server 0.3kB/s TCP to server 0.0kB/s UDP to server

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Results: 84.4 positions/minute

    Oct 18 15:53:34 raspberrypi adsbexchange-mlat[31848]: Aircraft: 5 of 13 Mode S, 9 of 11 ADS-B used

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Receiver status: connected

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Server status: ready

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Receiver: 152.4 msg/s received 38.1 msg/s processed (25%)

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Server: 0.1 kB/s from server 0.4kB/s TCP to server 0.0kB/s UDP to server

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Results: 73.8 positions/minute

    Oct 18 16:08:34 raspberrypi adsbexchange-mlat[31848]: Aircraft: 6 of 12 Mode S, 9 of 13 ADS-B used
     
  2. wiedehopf

    wiedehopf Administrator Staff Member

    You're feeding.

    /myip should also be working by now.
    If it's not, you have some weird internet or maybe using separate internet access to access /myip?
     
  3. Dutchyb

    Dutchyb New Member

    still not working.

    I am not using a different internet. So must be a weird internet connection. One last equation:
    Is it possible to change the internal IP address.

    If not I would like to thank you for all your time. Guess I have taken enough of your time. If the change of IP address is not working I will uninstall the feed as it is perfectly working for my 5 other feeds.
    Thanks
    Bert

    Found it, when I disable my VPN it is working. Weird as I have my VPN enabled for the other feeds. So please if you know a way to change the internal address it would be highly appreciated.
     
  4. wiedehopf

    wiedehopf Administrator Staff Member

    which is the base image?

    for Raspbian you can just google a guide.
    for piaware sd-card image you can check the FA forums or the readme for that.
     
  5. Dutchyb

    Dutchyb New Member

    Thank you for the time (again)

    Will have to search and try to find how to detect what base image I use.
     
  6. Dutchyb

    Dutchyb New Member

    Good afternoon,

    have been searching the internet how to find the base image I use.

    My best guess is the one used by Flightradar24, because that is the one I installed first. Hope this makes sense?
     
  7. wiedehopf

    wiedehopf Administrator Staff Member

  8. Dutchyb

    Dutchyb New Member

    Sorry for such pain in the....

    That is exactly what I did a long time ago. My Pi has IP 192.168.xxx.xxx I assigned this address to my Pi.
    My provider has given me 185.238.xxx.xxx

    When I enable my VPN service it uses different addresses. Most used 31.6.xxx.xxx

    When I disable my service, ADSBexchange my ip shows the 185.238 IP address.
    My other feeders us the 192.168 Ip addresses. So for me it is getting very confusing.

    But the good thing is I am actually feeding to the ADSB server:):)
     
  9. wiedehopf

    wiedehopf Administrator Staff Member

    It's not the IP address of the RPi .... the /myip page shows the IP for your internet connection, you can't change that.
     
  10. Dutchyb

    Dutchyb New Member

    Thank you again for the reply.
    So starting all over won't solve this"problem"

    Will keep it the way it is.
    Thanks for all your time and help
     
  11. wiedehopf

    wiedehopf Administrator Staff Member

    No, but apparently there is no problem to begin with :)
     
  12. Dutchyb

    Dutchyb New Member

    Sorry for the late respons.
    No other " problem" than I have to disable my VPN service:(
     
  13. wiedehopf

    wiedehopf Administrator Staff Member

    Just bookmark the links on the /myip page?
    It's not like you need to visit it daily?
     
  14. James

    James Guest

    Why would you need to disable VPN? ... because /myip doesn't work?

    So feed over the VPN ...

    We can't change how the Internet works. That technology was decided many years ago and we have no control over that.

    If you install stats, then just bookmark the links to your feed stats and map.

    Then you can use your VPN and view relay data ... I guess .. not sure what the issue is really ..

    Once feed is setup, it just works 99.99% of the time there is no need to check /myip daily