Unable to feed

Discussion in 'Feeding' started by XM192, Apr 25, 2018.

  1. XM192

    XM192 New Member

    I've not appeared in the stats for a while. On checking /var/log/syslog I see:

    Had to remove the log as I can't submit the message because with the logging it's rejected for looking like spam.

    but it's roughly lost connection to feed.<adsb> on port 3109
    reconnecting in 16 seconds
    connected
    handshakinging
    lost connection...

    I've run setup.sh again and still does it. Is there something I need to change?

    Regards Rob.
     
  2. MDA

    MDA Administrator Staff Member

    Be patient. Depending on region and quality of your internet connection it can take hours.
     
  3. XM192

    XM192 New Member

    I don't think I've connected for at least a month. I get:

    Disconnecting from <URL>:31090: No data (not even keepalives) received for 60 seconds

    I have to change the server to <URL> to stop this message being rejected for spam.

    I've got a 80mb/sec Infinity2 (business) line..
     
  4. MDA

    MDA Administrator Staff Member

    How many aircrafts/hour can you see and are there other feeders in your neighbourhood?
     
  5. James

    James Guest

    Odd. 31090 is MLAT server ... what image are you using?

    try pinging the MLAT server from the pi

    ping -p 31090 feed.adsbexchange.com
     
  6. XM192

    XM192 New Member

    I'm not sure what the image was but it had been working for about a year and is now reporting as 3.5.0. I have one other feeder who is about five miles away.

    I think I might wipe it and re-install.
     
  7. James

    James Guest

    Must be an old version of the Piaware image. MLAT is going to get upgraded once we secure some funds for it - as of right now that's just the connection loop - it will connect. There's nothing wrong with you image , it's probably just our MLAT being flaky.
     
  8. heliosh

    heliosh New Member

    Same here. Ran for days, no success.

    Code:
    Connected to multilateration server at feed adsbexchange com:31090, handshaking
    Beast-format results connection with 127.0.0.1:30104: connection established
    Lost connection to feed adsbexchange com:31090
    Reconnecting in 30.0 seconds
    Connected to multilateration server at feed adsbexchange com:31090, handshaking
    Lost connection to feed adsbexchange com:31090
    Reconnecting in 30.0 seconds
    Goes on forever.
    (I had to remove the dots from feed adsbexchange com because otherwise i couldn't post the message due to spam warning)
     
  9. James

    James Guest

    It will connect.

    You're likely just on an overloaded slice. We need to increase the slices but that takes a 5Ghz gaming server and MLAT is single threaded python application.
     
  10. heliosh

    heliosh New Member

    I went through the entire log and indeed it was connected twice. But after some minutes I get:

    Code:
    Wed Jul  4 07:13:02 2018 Disconnecting from feed[DOT]adsbexchange[DOT]com:31090: No data (not even keepalives) received for 60 seconds
    And the whole thing starts again. This way I can feed about an hour per day.
     
    Last edited: Jul 4, 2018
  11. MDA

    MDA Administrator Staff Member

    Not really, your feeder will be used for 1 hour to calculate MLAT positions, ADSB feed should work all the time.
     
  12. MDA

    MDA Administrator Staff Member

    You are right, your feeder is not connected to MLAT server. But you are probably still feeding ADSB data. Look at:
    (your path - depending on install you use)/adsbexchange-netcat_maint.sh
    If you don't use custom port you should be connected to feed.adsbexchange.com:30005
     
  13. heliosh

    heliosh New Member

    I'm not feeding ADSB. We have no interesting non-MLAT traffic worthwhile to feed and the coverage should be already pretty well.
     
  14. MDA

    MDA Administrator Staff Member

    If you have ADSBx MLAT client installed then you are feeding ADSB data too. If your install is non standard (netcat script removed fe.) then you can only try to feed MLAT data. If your feeder is delivering poor quality/ low amount of data it will be kicked-out automatically by MLAT server. Server has limited capability, we have to accept it.
    Thanks for feeding, but if you are not happy with it it you can stop. This is non-commercial website. We are all volunteers, not paid by any other person.
     
  15. James

    James Guest

    Seems more like you weren't synced with any other feeders or something. Thanks for feeding, there is no reason to get emotional and throw a temper tantrum. There are quite a few people not setting up the lat/long correctly and that will make it so no feeders are near them.

    I think I'm going to turn off logging on these images, too many people get too concerned with the smallest things instead of seeing the bigger picture and letting the feeder send traffic.
     
  16. heliosh

    heliosh New Member

    Why do you think I was being emotional?
    My feeder was synced and the timings were ok. But sometimes there is not much traffic since i basically live in the middle of the alps with limited range due to the mountains.
    It's comprehensible that you rather give the (limited) slices to feeders with better coverage.
     
  17. James

    James Guest

    If you are filling a gap then you are helping the ADSBx community. There are feeders in Africa that only track 2 planes a month.