Announcement

Collapse
No announcement yet.

client crashing after awhile, linux + mr-dump1090

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

  • client crashing after awhile, linux + mr-dump1090

    my previously stable setup went unstable without me knowing, now that key is gone so I was given a new key.
    this new configuration is unstable,
    it crashes out and with no more service 127.0.0.1:8754
    after this crash I
    Code:
    # sudo service fr24feed status
    it reports
    Code:
    Aug 06 13:23:46 nc4400 systemd[1]: fr24feed.service: Found left-over process 19462 (mr-dump1090) in control group while starting unit. Ignoring
    Aug 06 13:23:47 nc4400 fr24feed[943]:  * Starting FR24 feeder fr24feed
    Aug 06 13:23:47 nc4400 fr24feed[943]:    ...done.
    Aug 06 13:23:46 nc4400 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
    Aug 06 13:23:46 nc4400 systemd[1]: Starting LSB: Flightradar24 Decoder & Feeder...
    i use mr-dump1090
    fr24 config
    proper key
    dvdb
    /usr/lib/fr24/mr-dump1090
    --net --net-http-port 38080
    RAW YES or NO

    as usual the above does start & stop mr-dump1080 on port 38080

    I've rebooted the machine and the service on 8754 dies after awhile, did this several times.

    any ideas how to fix?


    also dmesg reports

    [ 102.306605] th_network_clie[1686]: segfault at 141fbbdc ip 00000000080abf8d sp 00000000f41fbb50 error 6 in fr24feed[8048000+a7000]
    ...
    [ 3519.904533] th_network_clie[3590]: segfault at 141fdbdc ip 00000000080abf8d sp 00000000f41fdb50 error 6 in fr24feed[8048000+a7000]
    [19873.246463] th_network_clie[19477]: segfault at 142fbbdc ip 00000000080abf8d sp 00000000f42fbb50 error 6 in fr24feed[8048000+a7000]
    [95869.872263] th_network_clie[2572]: segfault at 142fdbdc ip 00000000080abf8d sp 00000000f42fdb50 error 6 in fr24feed[8048000+a7000]
    Last edited by galenthurber; 2019-08-06, 17:18. Reason: segfaults

  • #2
    you could try disabling ipv6, explained somewhere in this forum.

    Anyway, mr-dump1090 is way outdated.
    I'd recommend starting with a fresh image/install.

    Comment


    • #3
      thank you I'll look for updates to mr-dump1090
      Last edited by galenthurber; 2019-08-07, 12:18. Reason: wrong paste

      Comment


      • #4
        No no, just do a complete reinstall.

        Your whole installation is outdated.

        You could for example follow this guide:
        https://forum.flightradar24.com/thre...ickStart-Guide

        Comment


        • #5
          "client crashing after awhile, linux + mr-dump1090"

          Wat is your hardware & OS?

          RPi + Pi24 image
          RPi + Raspbian image
          Intel or Mac PC + Linux x86_64 (Debian, Ubuntu etc)

          Comment


          • #6
            Xubuntu 64
            dvbt flightaware with its internal amp
            this was a stable setup with mr-dump1090 recently it started SEGfaulting
            changed to dump1090-mutability and
            fr24feed is crashing out


            SEGfaulting in dmesg
            th_network_clie[7845]: segfault at 13afabdc ip 00000000080abf8d sp 00000000f3afab50 error 6 in fr24feed[8048000+a7000]

            I'll reinstall fr24feed software
            and try to get flightaware 1090 feeder working

            Comment


            • #7
              This somehow sounds like your hard drive is dying.

              Two programs starting to segfault most likely means something is wrong with the hardware.

              Comment


              • #8
                tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 775/fr24feed
                tcp 0 0 0.0.0.0:30003 0.0.0.0:* LISTEN 775/fr24feed
                tcp 0 0 0.0.0.0:30053 0.0.0.0:* LISTEN 1206/pfclient
                tcp 0 0 0.0.0.0:30054 0.0.0.0:* LISTEN 1206/pfclient
                tcp 0 0 0.0.0.0:8754 0.0.0.0:* LISTEN 775/fr24feed
                tcp 0 0 0.0.0.0:http 0.0.0.0:* LISTEN 32705/lighttpd

                no tcp6

                Comment


                • #9
                  Code:
                  dmesg 
                  [uptime] th_network_clie[2518]: segfault at 13afbbdc ip 00000000080abf8d sp 00000000f3afbb50 error 6 in fr24feed[8048000+a7000]
                  version 1.0.18-15

                  I will try again purge fr24feed
                  and reinstall it

                  Comment


                  • #10
                    just to be sure I'm checking with systemctl [systemd] & system V [service]
                    Code:
                    sudo systemctl status fr24feed 
                    ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
                       Loaded: loaded (/etc/init.d/fr24feed; generated)
                       Active: active (exited) since Sun 2019-08-11 06:39:13 ADT; 6min ago
                         Docs: man:systemd-sysv-generator(8)
                      Process: 23535 ExecStop=/etc/init.d/fr24feed stop (code=exited, status=0/SUCCESS)
                      Process: 23545 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
                    
                    systemctl status dump1090-mutability
                    ● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
                       Loaded: loaded (/etc/init.d/dump1090-mutability; generated)
                       Active: active (exited) since Sun 2019-08-11 06:43:13 ADT; 4min 23s ago
                         Docs: man:systemd-sysv-generator(8)
                      Process: 23245 ExecStop=/etc/init.d/dump1090-mutability stop (code=exited, status=0/SUCCESS)
                      Process: 23804 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)
                    
                    Aug 11 06:43:12 nc4400 systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                    Aug 11 06:43:13 nc4400 systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                    but no control nor open port 8754

                    I wonder if there is a new systemd syntax for Xubuntu 18.04 ? why the false positives [ACTIVE] for service that is not running?
                    Last edited by galenthurber; 2019-08-11, 10:10. Reason: grammar

                    Comment


                    • #11
                      just to be sure I'm checking with systemctl [systemd] & system V [service]
                      [code]
                      sudo systemctl status fr24feed
                      ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
                      Loaded: loaded (/etc/init.d/fr24feed; generated)
                      Active: active (exited) since Sun 2019-08-11 06:39:13 ADT; 6min ago
                      Docs: man:systemd-sysv-generator(8)
                      Process: 23535 ExecStop=/etc/init.d/fr24feed stop (code=exited, status=0/SUCCESS)
                      Process: 23545 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)

                      systemctl status dump1090-mutability
                      ● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
                      Loaded: loaded (/etc/init.d/dump1090-mutability; generated)
                      Active: active (exited) since Sun 2019-08-11 06:43:13 ADT; 4min 23s ago
                      Docs: man:systemd-sysv-generator(8)
                      Process: 23245 ExecStop=/etc/init.d/dump1090-mutability stop (code=exited, status=0/SUCCESS)
                      Process: 23804 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)

                      Aug 11 06:43:12 nc4400 systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                      Aug 11 06:43:13 nc4400 systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                      [code]

                      but no control nor open port 8754

                      I wonder if there is a new systemd syntax for Xubuntu 18.04 ? why the false positives for ACTIVE?

                      Comment


                      • #12
                        purge and fresh install of fr24feed,
                        Code:
                        dmesg
                         th_network_clie[18250]: segfault at 142fcbdc ip 00000000080abf8d sp 00000000f42fcb50 error 6 in fr24feed[8048000+a7000]
                        feeder is still segfaulting

                        Comment


                        • #13
                          update:
                          too unstable

                          feeder is creating massive log files
                          2048MB for example

                          loads of
                          Code:
                          2019-08-18 14:50:38 | [raw][w]Too many connections!
                          2019-08-18 14:50:39 | [raw][w]Too many connections!
                          2019-08-18 14:50:40 | [raw][w]Too many connections!
                          2019-08-18 14:50:41 | [raw][w]Too many connections!
                          2019-08-18 14:50:42 | [raw][w]Too many connections!
                          2019-08-18 14:50:43 | [raw][w]Too many connections!
                          2019-08-18 14:50:44 | [raw][w]Too many connections!
                          2019-08-18 14:50:45 | [raw][w]Too many connections!
                          2019-08-18 14:50:46 | [feed][n]ping 1
                          2019-08-18 14:50:46 | [raw][w]Too many connections!
                          2019-08-18 14:50:47 | [feed][n]syncing stream: 1
                          2019-08-18 14:50:47 | [raw][w]Too many connections!
                          2019-08-18 14:50:48 | [raw][w]Too many connections!
                          2019-08-18 14:50:49 | [raw][w]Too many connections!
                          2019-08-18 14:50:50 | [raw][w]Too many connections!
                          2019-08-18 14:50:51 | [raw][w]Too many connections!
                          2019-08-18 14:50:52 | [raw][w]Too many connections!

                          Comment


                          • #14
                            That's why it's recommended to only turn on logs for diagnosis.

                            That error, is probably too many connections to 30002/30334

                            As I pointed out in your other thread with the same ports listed. You had the server options enabled in fr24feed config. And not dump1090 (--net_ which can handle more simultaneous connections.
                            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                            Comment


                            • #15
                              Open /etc/fr24feed.ini and change bs and raw to no:

                              bs="no"
                              raw="no"

                              Add or modify the procargs so it looks like this:

                              procargs="--net"

                              Restart fr24feed

                              Now you can connect your other software to the ports offered by dump1090:
                              AVR on 30002
                              SBS Basestation on 30003
                              Beast on 30005

                              Comment

                              Working...
                              X