Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: client crashing after awhile, linux + mr-dump1090

  1. #1
    Passenger
    Join Date
    Sep 2018
    Location
    St Ann's Bay or Timberlea Nova Scotia
    Posts
    37

    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 at 17:18. Reason: segfaults

  2. #2
    Captain
    Join Date
    Apr 2018
    Posts
    752
    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.

  3. #3
    Passenger
    Join Date
    Sep 2018
    Location
    St Ann's Bay or Timberlea Nova Scotia
    Posts
    37
    thank you I'll look for updates to mr-dump1090
    Last edited by galenthurber; 2019-08-07 at 12:18. Reason: wrong paste

  4. #4
    Captain
    Join Date
    Apr 2018
    Posts
    752
    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

  5. #5
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,769
    "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)

  6. #6
    Passenger
    Join Date
    Sep 2018
    Location
    St Ann's Bay or Timberlea Nova Scotia
    Posts
    37
    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

  7. #7
    Captain
    Join Date
    Apr 2018
    Posts
    752
    This somehow sounds like your hard drive is dying.

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

  8. #8
    Passenger
    Join Date
    Sep 2018
    Location
    St Ann's Bay or Timberlea Nova Scotia
    Posts
    37
    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

  9. #9
    Passenger
    Join Date
    Sep 2018
    Location
    St Ann's Bay or Timberlea Nova Scotia
    Posts
    37
    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

  10. #10
    Passenger
    Join Date
    Sep 2018
    Location
    St Ann's Bay or Timberlea Nova Scotia
    Posts
    37
    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 at 10:10. Reason: grammar

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •