Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

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

  1. #11
    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).
    [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?

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

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

  4. #14
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,032
    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

  5. #15
    Captain
    Join Date
    Apr 2018
    Posts
    842
    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

  6. #16
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,032
    I probably should have elaborated. But it was stupid o'clock and many of the guides here list the preferred method of use

    Basically, as we've discovered over time and subsequently now advise users. Letting fr24feed CONTROL a USB stick, (like presumably you are) by calling up it's own decoder etc is less than ideal - UNLESS, it is the only feed destination you wish to provide (no other requirement for the data it produces) or can ensure the system won't have issues or need to re-attach to the device. Especially when the generic linux version is so many editions behind.

    It has issues passing through errors to the dump1090 it launches
    It can't handle more than 2-3 connections on any open ports it opens

    The better way, is a 3rd party decoder. That is crash-aware and further/better developed than the dump1090-mr version (and later 1.14), and attach fr24feed to data it produces via data port - just like other apps/feeders

    Best course of action. Remove fr24feed.
    Find a Dump1090 version that will install on your OS.
    Run it, test it for a day or 2 (internal map web page). Make sure the USB stick stays constant, and can be rebooted and start automatically

    Only then, Install FR24feed (and others) - But *** DON'T SELECT DVBT **
    Let it discover (or manually adjust) to network based data source.

    Chances are, your crashing/USB issues will likely vanish as fr24feed sits there dumb just listening
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

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
  •