Announcement

Collapse
No announcement yet.

TESTED - "1.0.24-5_amd64" and "1.0.24-5_i386"

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

  • TESTED - "1.0.24-5_amd64" and "1.0.24-5_i386"

    Case 1 of 4: Linux .deb package: fr24feed_1.0.24-5_amd64.deb

    Installed by:
    Code:
    wget -O ~/fr24feed_1.0.24-5_amd64.deb https://repo-feed.flightradar24.com/linux_x86_64_binaries/fr24feed_1.0.24-5_amd64.deb
    sudo dpkg -i fr24feed_1.0.24-5_amd64.deb
    DISTRO STARTED WITH SYSTEMD
    sudo systemctl start fr24feed
    STARTED DIRECTLY
    sudo fr24feed
    Debian 10.1 amd64

    AND

    Ubuntu 18.04 amd64
    If mlat="no", OK

    If mlat="yes", perpetual restart with following message:

    [e]PacketSenderConfiguration::fetch_config(): Unable to parse jsoned response
    [d]TLSConnection::ctor(): Enable verify_peer in production code!

    [i]Timestamp source changed from UNKNOWN to SYSTEM-UNCERTAIN
    [i]Synchronizing time via NTP
    [w]Failed to synchronize time, waiting 8 seconds
    [i]Synchronizing time via NTP
    [w]Failed to synchronize time, waiting 16 seconds
    If mlat="no", OK

    if mlat="yes", Segmentation fault and stopped.

    [e]PacketSenderConfiguration::fetch_config(): Unable to parse jsoned response
    [d]TLSConnection::ctor(): Enable verify_peer in production code!
    ..... ....
    [i]Timestamp source changed from SYSTEM-UNCERTAIN to SYSTEM-VALIDATED
    .... ....
    [i]Feed connected
    [n]working
    [i]sent 1,0 AC
    Segmentation fault
    .
    .


    Case 2 of 4: Linux .deb Package: fr24feed_1.0.24-5_i386.deb

    Installed by:
    Code:
    sudo dpkg --add-architecture i386
    sudo apt update
    sudo apt install gcc-8-base:i386 libc6:i386 libgcc1:i386 libstdc++6:i386
    
    wget -O ~/fr24feed_1.0.24-5_i386.deb https://repo-feed.flightradar24.com/linux_x86_binaries/fr24feed_1.0.24-5_i386.deb
    
    sudo dpkg -i fr24feed_1.0.24-5_i386.deb
    DISTRO STARTED WITH SYSTEMD
    sudo systemctl start fr24feed
    STARTED DIRECTLY
    sudo fr24feed
    Debian 10.1 amd64

    AND

    Ubuntu 18.04 amd64
    If mlat="no", OK

    If mlat="yes", perpetual restart with following message:

    [e]PacketSenderConfiguration::fetch_config(): Unable to parse jsoned response
    [d]TLSConnection::ctor(): Enable verify_peer in production code!

    [i]Timestamp source changed from UNKNOWN to SYSTEM-UNCERTAIN
    [i]Synchronizing time via NTP
    [w]Failed to synchronize time, waiting 8 seconds
    [i]Synchronizing time via NTP
    [w]Failed to synchronize time, waiting 16 seconds
    If mlat="no", OK

    if mlat="yes", Segmentation fault and stopped.

    [e]PacketSenderConfiguration::fetch_config(): Unable to parse jsoned response
    [d]TLSConnection::ctor(): Enable verify_peer in production code!
    ..... ....
    [i]Timestamp source changed from SYSTEM-UNCERTAIN to SYSTEM-VALIDATED
    .... ....
    [i]Feed connected
    [n]working
    [i]sent 1,0 AC
    Segmentation fault
    .
    .


    Case 3 of 4: Linux Archive: fr24feed_1.0.24-5_amd64.tgz

    Installed by:
    Code:
    ## OpenSUSE
    sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/fr24feed-debian-ubuntu-amd64/master/install-OpenSUSE-fr24feed_1.0.24-5_amd64.tgz.sh)"
    
    
    ## Arch Linux
    sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/fr24feed-debian-ubuntu-amd64/master/install-ArchLinux-fr24feed_1.0.24-5_amd64.tgz.sh)"
    DISTRO STARTED WITH SYSTEMD
    sudo systemctl start fr24feed
    STARTED DIRECTLY
    sudo fr24feed
    OpenSUSE
    Leap 15.1
    amd64
    OK with and without mlat OK with and without mlat
    Arch Linux
    amd64
    Fails with and without mlat

    Active: failed (Result: core-dump)
    Process: 1889 ExecStart=/usr/bin/fr24feed (code=dumped, signal=SEGV)
    Main PID: 1889 (code=dumped, signal=SEGV)

    archlinux systemd[1]: fr24feed.service: Failed with result 'core-dump'.
    archlinux systemd[1]: Failed to start Flightradar24 Feeder.
    Fails with and without mlat.
    Segmentation fault and stopped.
    .
    .


    Case 4 of 4: Linux Archive: fr24feed_1.0.24-5_i386.tgz

    Installed by:
    Code:
    ## OpenSUSE
    sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/fr24feed-debian-ubuntu-amd64/master/install-OpenSUSE-fr24feed_1.0.18-5_amd64.tgz.sh)"
    
    
    ## Arch Linux
    sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/fr24feed-debian-ubuntu-amd64/master/install-ArchLinux-fr24feed_1.0.24-5_i386.tgz.sh)"
    DISTRO STARTED WITH SYSTEMD
    sudo systemctl start fr24feed
    STARTED DIRECTLY
    sudo fr24feed
    OpenSUSE
    Leap 15.1
    amd64
    OK with and without mlat OK with and without mlat
    Arch Linux
    amd64
    OK with and without mlat OK with and without mlat
    Last edited by abcd567; 2019-11-21, 19:17.

  • #2
    This explains my test results:

    Originally posted by SlashbNL View Post
    After mailing with FR24 Support they told me only MLAT data is used from Raspberry Pis with dvbt dongles and their shipped receivers.

    Comment


    • #3
      I don't know how or why (maybe one of the apt-get upgrades?) my FR24 install on Ubuntu AMD64 (i386 package) stopped serving the [IP]:8754 status page.
      The feeder status also shows 0 planes tracked like before (MLAT is deactivated by me), but it still sends data to FR24 servers:

      sorin@Ubuntu-Latitude-E6420:~$ fr24feed-status
      * FR24 Feeder/Decoder Process: running
      * FR24 Stats Timestamp: 2019-12-09 10:33:18
      * FR24 Link: connected [UDP]
      * FR24 Radar: T-KPHF1
      * FR24 Tracked AC: 0
      * Receiver: connected (7334845 MSGS/0 SYNC)
      * FR24 MLAT: not running
      Last edited by SoNic67; Yesterday, 10:39.

      Comment

      Working...
      X