Recent content by Christopher Robert

  1. C

    Failed TCP connection to all provided addresses

    There were no more activities necessessary, the ADS-B programs are now running stable. But I need a hardware-upgrade. My raspberry-activities have grown with the time, one small job after another came (DNS-Filter, firewall, printserver, NAS for backups, now ADS-B). Its time that the busy but...
  2. C

    Failed TCP connection to all provided addresses

    cat /etc/fr24feed.ini receiver="beast-tcp" fr24key="*************" host="127.0.0.1:30005" bs="no" raw="no" logmode="1" logpath="/var/log/fr24feed" mlat="yes" mlat-without-gps="yes" http-timeout=20 cat /etc/rbfeeder.ini [client] network_mode=true log_file=/var/log/rbfeeder.log...
  3. C

    Failed TCP connection to all provided addresses

    Yes, but the decoder (dump1090) must correspond to the dongle. And when the feeder expects data on port 30005 (like planefinder) and the decoder delivers them on 30002, the feeder cant feed usable data. Something like that will be the cause when my feeders feed after 22:00 empty feeds. I...
  4. C

    Failed TCP connection to all provided addresses

    Raspbian Stretch Lite with XFCE-Desktop. I'm single, and single user. The rest of the internet-connections are still working, only the ADS-B-feeders (based on dump1090) are sending feeds without data. For example radarscape marks in the statistics the status online, transmitted data zero. The...
  5. C

    Failed TCP connection to all provided addresses

    For the moment everything is working good. Only one thing looks a bit strange: Every day at 22:00 all ads-b-feeds begin to feed only empty data; after a reboot its okay. I havent found why, but I havent searched deeply. My workaround is a cronjob that reboots daily the raspi at 22:01. ;-) That...
  6. C

    Failed TCP connection to all provided addresses

    Thanks, that looks good. In my fr24feed.ini the receiver was "avr-tcp". This seems to conflict witth the planefinder configuration as beast.
  7. C

    Failed TCP connection to all provided addresses

    After finally having resolved the signature-problems with radarbox24 and updated the rbclient, I had some new errors with the pflient: 2019-02-01 14:18:54.647061 [-] Failed TCP connection to all provided addresses for: 127.0.0.1:30005 2019-02-01 14:18:54.646854 [V] Failed to open connection to...
  8. C

    Failed TCP connection to all provided addresses

    Finally it works! apt-cache policy dump1090 didnt show me the installation but it was installed (by make and not by apt, so it will not be shown by apt). I could not unistall dump1090 correcly, and had problems with the concurrent installation of dump1090 and dump1090-mutability . So I tried a...
  9. C

    Failed TCP connection to all provided addresses

    Update: After a restart of the raspi (sudo reboot) the pflient connects: 2019-01-29 11:18:17.102548 [-] TCP connection established: 127.0.0.1:30005 2019-01-29 11:18:17.101760 [-] Client restarted successfully 2019-01-29 11:18:17.101659 [-] Closed TCP connection: 127.0.0.1:30005 2019-01-29...
  10. C

    Failed TCP connection to all provided addresses

    Hello First I checked if there were different versions of dump1090 installed: apt-cache policy dump1090-fa apt-cache policy mr-dump1090 apt-cache policy dump1090 apt-cache policy dump1090-mutability Only dump1090-mutability was installed. So I made a clean uninstall: sudo systemctl disable...
  11. C

    Failed TCP connection to all provided addresses

    Hi I Installed and configurated my feeder following https://forum.planefinder.net/threads/raspberry-pi-b-rpi2-rpi3-installation-instructions-for-raspbian-dump1090-data-feeder.241/#post-2451 But the feeder isnt working and in the logs I get all 5 seconds an error like 2019-01-28 16:40:01.466343...
Top