Announcement

Collapse
No announcement yet.

feeder 1.0.18-5 stalling on Linux64. gui not responding 127.0.0.1:8754 mr-dump

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • feeder 1.0.18-5 stalling on Linux64. gui not responding 127.0.0.1:8754 mr-dump

    I'm using mr-dump1090 via fr24feeder

    Oct 16th gui started stalling, not loading.
    Data was being fed out to 30005
    30001-3005 all are listening

    I noticed "my stats" page shows me as connected then goes offline & stays offline even when dump1090 on :8080 shows data
    my planefinder stats still is active.

    Oct 16th I noticed error in retrieving my stats page

    My /var/log/fr24feed.log/
    reports
    2018-10-17 09:03:53 | ERROR
    2018-10-17 09:03:53 | [w]Detected --net argument for dump1090, disabling internal RAW feed!
    2018-10-17 09:03:53 | [w]Detected --net argument for dump1090, disabling internal BS feed!
    2018-10-17 09:03:53 | [httpd][e]bind function failed, errno: 98
    2018-10-17 09:03:53 | [httpd][d]Master thread terminated
    2018-10-17 09:03:53 | [main][i]Reader thread started
    2018-10-17 09:03:53 | [time][i]Synchronizing time via NTP
    2018-10-17 09:03:53 | [master][i]Starting processing thread
    2018-10-17 09:03:53 | [reader][i]Initializing reader
    2018-10-17 09:03:53 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/mr-dump1090 --net-beast --net --raw)
    2018-10-17 09:03:53 | [reader][i]Connected to the receiver, configuring
    2018-10-17 09:03:53 | [reader][i]Configured, processing messages
    2018-10-17 09:03:53 | [reader][i]Connection terminated
    2018-10-17 09:03:53 | [main][i]Terminating child process 3286 with SIGETERM
    2018-10-17 09:03:59 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/mr-dump1090 --net-beast --net --raw)
    2018-10-17 09:03:59 | [reader][i]Connected to the receiver, configuring
    2018-10-17 09:03:59 | [reader][i]Configured, processing messages
    2018-10-17 09:03:59 | [reader][i]Connection terminated

    I removed --net in the .ini
    mr-dump1090 --net-beast --raw

    #sudo fr24feed stop
    #sudo service fr24feed stop
    #sudo service fr24feed status
    #sudo service fr24feed start

    still gui is not loading or feeding

    ideas?

  • #2
    Try to:

    sudo service fr24feed stop

    sudo killall mr-dump1090

    /usr/lib/fr24/mr-dump1090 --net --interactive


    Change settings in your file /etc/fr24feed.ini:

    receiver="beast-tcp"
    fr24key="(your FR24 key)"
    host="localhost:30005"

    and then

    sudo service fr24feed start
    Last edited by SQ5IRZ; 2018-10-18, 21:32.

    Comment


    • #3
      My fr24feed is misbehaving,
      sudo fr24feed stop
      will not work, it actually tries to restart the feeder.

      I have to
      sudo killall mr-dump1090
      first or else RTL is reported busy

      I'll try more configurations; note that dump1090 gui on 8080 is stalling. I've tried it another port --http-net-port 38080, and still no access via browser, just stalls or hangs
      Last edited by galenthurber; 2018-10-17, 21:21.

      Comment


      • #4
        fr24feed only responds to certain commands. 'Stop' is not one of them without 'service' or using systemctl version of it - sudo systemctl stop fr24feed

        All that will do is re-launch it and try start dump1090 again when it is obviously already running.

        https://forum.flightradar24.com/thre...ll=1#post74851


        If you dont fully understand how the USB stick is accessed and accidentally install another providers feeder package/incorrectly configured. Or choose DVBT at any stage in fr24feed settings, the normal dump1090 you have running may be effected.

        Remember depending on options, you can run dump1090 automatically on start of device OR launch it by starting fr24feed. (which should also stop when you close/stop the feeder)

        Get it round the wrong way, and the above happens when it isn't connecting to a live feed. But trying to re-launch it when its already active.
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          First REBOOT. This will stop multiple instances of feeder/dump1090, then will restart properly single instances.

          Code:
          sudo reboot
          After reboot, do NOT give any command in console. Wait for 5 minutes, then check in BROWSER:

          Status on:
          localhost:8754
          127.0.0.1:8754

          Map on:
          localhost:8080
          localhost/dump1090/gmap.html
          127.0.0.1/dump1090/gmap.html
          Last edited by abcd567; 2018-10-18, 02:53.

          Comment


          • #6
            Originally posted by abcd567 View Post
            First REBOOT. This will stop multiple instances of feeder/dump1090, then will restart properly single instances.

            Code:
            sudo reboot
            After reboot, do NOT give any command in console. Wait for 5 minutes, then check in BROWSER:

            Status on:
            localhost:8754
            127.0.0.1:8754

            Map on:
            localhost:8080
            localhost/dump1090/gmap.html
            127.0.0.1/dump1090/gmap.html
            yes, waiting is a good thing.
            I've made sure daemons are shutdown, then use
            #sudo service fr24feed start
            but that has been unreliable the last few days, especially in that it will not start dump1090 at all.
            mrdump1090 is what I use anyways.
            There might be some caching going on that needs flushing, PIDs or something.
            I've found if I change a setting inside fr24feed's webgui it takes two restarts to change the live settings.
            I'll watch
            #sudo netstat -t -p -l
            to watch the daemons go up and down.
            Last edited by galenthurber; 2018-10-18, 20:33.

            Comment


            • #7
              sudo service fr24feed start

              Above command will (most likely) start a 2nd instance.
              Dont use start
              Use restart

              The restart command first shutdowns running instance, then starts a new instance.
              Last edited by abcd567; 2018-10-18, 21:21.

              Comment

              Working...
              X