Page 5 of 22 FirstFirst ... 3456715 ... LastLast
Results 41 to 50 of 213

Thread: Archived: Feed issues with 19-2

  1. #41
    Flight attendant
    Join Date
    Jun 2015
    Posts
    62
    Hello everyone,

    Sorry for the latest disruptions and thanks a lot for your feedback, it is absolutely valuable and helpful!
    As you see, there are lots of different platforms to support and even automated testing doesn't always find all possible issues. But we are working hard!

    Regarding NTP or similar issues - we have an RPi unit running Jessie but can't reproduce any issues with running fr24feed as nobody. Could you please provide more details, was the OS somehow modified, e.g. security-wise?

  2. #42
    Team FR24
    Join Date
    Feb 2015
    Posts
    220
    @Oblivian, @abcd567, @mgunther and all others that I haven't mentioned directly, thanks a lot for your help and feedback. It helps immensely. We will continue to make improvements to the software.
    --

  3. #43
    Passenger
    Join Date
    Mar 2017
    Location
    GCLA
    Posts
    18
    Quote Originally Posted by Oblivian View Post
    User here in NZ said he has an untouched unit that self upgraded about UTC 0700 update yesterday, from 18-9 -> 19-2 -> 19.5 with no intervention as far as we are aware, and while his USB unit started OK. the Beast unit has not. And that doesn't even call Dump1090. So unless running the install/update as not sudo somewhere has done it..

    https://forum.flightradar24.com/thre...l=1#post100597

    /edit unless its stretch. That's had some drastic changes and now what RPi consider 'stable' over jessie.
    This morning (24/01) I woke up and found my fr24feed down again.
    It had automatically been updated to version 1.0.19-6 at around 06 UTC, time when it went down again !

    Same problem with permissions but this time I could fix it in 10 minutes.

    Now its back.

    Linux/generic/static_arm/1.0.19-6
    Updated: 09:15:45 GMT+0000 (GMT Standard Time)

    Cheers
    Orange Pi PC Plus + NooElec NESDR SMArt + homemade 6 ele CoCo

  4. #44
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,008
    Quote Originally Posted by hazchem View Post
    After this problem spent hours formatting and installing version 1.0.18-9 all running fine on my raspberry pi only to find this morning version 1.0.19-6 update has taken me down again another working update is required
    Do same commands as suggested here please.
    https://forum.flightradar24.com/thre...l=1#post100597

    And does it work when you go
    sudo service fr24feed stop
    sudo fr24feed

    Instead?
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  5. #45
    Flight attendant
    Join Date
    Jun 2015
    Posts
    62
    Additionally to what Oblivian suggested, it would be very helpful to get output of the following commands please:

    cat /etc/default/dump1090-mutability

    fr24feed --version

    cat /var/log/fr24feed/fr24feed.log

    cat /dev/shm/decoder.txt

    ls -al /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt /run/dump1090-mutability /usr/lib/fr24

    cat /etc/fr24feed.ini | grep -v fr24key

    ps aufx | grep -e fr24 -e dump1090

    sudo systemctl status fr24feed

    /usr/lib/fr24/dump1090 --help 2>&1 | grep dump1090

    sudo grep -e fr24feed -e dump1090 /var/log/syslog
    Last edited by vinnyspb; 2018-01-24 at 12:19. Reason: added few more commands

  6. #46
    Passenger
    Join Date
    Jan 2018
    Location
    T-LEPP7, Spain
    Posts
    16
    Your test for the type of installation "receiver=" can still fail.

    if grep -q "^receiver.*dvbt" /etc/fr24feed.ini - will match "receiver=avr-tcp #dvb" which is a valid way to edit the config file. A better idea might be:

    . /etc/fr24feed.ini
    if [ "$receiver" = dvbt ] ...

    Also, you are still setting a directory (/run/dump1090-mutability) to 777 permissions. Not safe. You should only create /run/fr24feed and /run/dump1090-mutability if they're required. In an installation using a stand-alone dump1090 they are not needed.

    Changing directory ownership and permissions of the files from one package from the systemd config of another is not a good idea. It can, and has, broken many things.

  7. #47
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,770
    YESTERDAY
    Re-imaged Raspbian Stretch Lite
    Installed dump1090-mutability v1.15~dev manually (click here)
    Installed fr24feed by bash script
    Code:
    pi@raspberrypi:~ $ sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)"
    .............
    gpg: keyserver receive failed: Server indicated a failure
    GPG key problem encountered on STRETCH only, NOT on JESSIE.
    Solved GPG key problem by manually installing the key (had to switch from pi to root to install the key)
    Code:
    pi@raspberrypi:~ $ sudo passwd root
    Enter new UNIX password:
    Retype new UNIX password:
    passwd: password updated successfully
    pi@raspberrypi:~ $ su root
    Password:
    root@raspberrypi:/home/pi# gpg --keyserver pool.sks-keyservers.net --recv-keys 40C430F5
    root@raspberrypi:/home/pi# gpg --armor --export 40C430F5 | apt-key add -  
    root@raspberrypi:/home/pi# mv /etc/apt/sources.list /etc/apt/sources.list.bak 
    root@raspberrypi:/home/pi# grep -v flightradar24 /etc/apt/sources.list.bak > /etc/apt/sources.list || echo OK
    root@raspberrypi:/home/pi# echo 'deb http://repo.feed.flightradar24.com flightradar24 raspberrypi-stable' >> /etc/apt/sources.list
    Ran perfectly well after following fix:
    Code:
    sudo nano /etc/systemd/system/fr24feed.service 
    #changed nobody:nogroup to dump1090:nogroup in line 12

    TODAY
    UPDATED FROM 1.0.19-5 to 1.0.19-6

    Code:
     
    sudo apt-get update
    apt-cache policy fr24feed
    fr24feed:
      Installed: 1.0.19-5
      Candidate: 1.0.19-6
    
    cd  /usr/lib/fr24/
    sudo ./fr24feed_updater.sh
    
    sudo apt-get update
    apt-cache policy fr24feed
    fr24feed:
      Installed: 1.0.19-6
      Candidate: 1.0.19-6
    FR24 1.0.19-6 on Stretch - Status.png FR24 1.0.19-6 on Stretch - map.png

    Running perfectly well WITHOUT any fix. Yesterday's fix in ver 1.0.19-5 in file /etc/systemd/system/fr24feed.service disappeared after update, and still everything is running perfectly well. Rebooted to make sure, still no problem. Here is the current fr24feed.service file

    Code:
    cat /etc/systemd/system/fr24feed.service
    
    [Unit]
    Description=Flightradar24 Decoder & Feeder
    After=network-online.target
    
    [Service]
    Type=simple
    Restart=always
    LimitCORE=infinity
    ExecStartPre=-/usr/lib/fr24/install_dump1090.sh
    ExecStartPre=-/bin/mkdir -p /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /var/log/lighttpd
    ExecStartPre=-/bin/touch /dev/shm/decoder.txt
    ExecStartPre=-/bin/chown -R nobody:nogroup /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt
    ExecStartPre=-/bin/chmod a+rwx /run/dump1090-mutability
    ExecStart=/usr/bin/fr24feed
    User=nobody
    Group=nogroup
    PermissionsStartOnly=true
    StandardOutput=null
    
    [Install]
    WantedBy=multi-user.target
    Last edited by abcd567; 2018-01-24 at 10:29.

  8. #48
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,008
    Managed to break mine now

    Similar spec, Piaware is happy again with .15-dev running, as is onboard map. But fr24feed won't connect to receiver out in either visual or service despite "Receiver: beast-tcp, Connected" on the web status

    Only difference is I did a apt-get install vs the bash. Seeing if it makes a difference now

    /edit.. ooh. Might be localhost no longer resolving. Which is probably a localised issue.. rejected by the setup wizard during setup 2nd time around and bash install

    And away again with all green this time (as avr client). Go figure

    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2018-01-24 10:57:03.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-NZCH26.
    [ ok ] FR24 Tracked AC:.
    [ ok ] Receiver: connected ( MSGS/ SYNC).
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 0.

    Change back to 'localhost:30002' as source..

    Code:
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2018-01-24 10:54:22.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-NZCH26.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    
    
    pi@raspberrypi:/usr/lib/fr24 $ cat /etc/hosts
    127.0.0.1       localhost
    ::1             localhost ip6-localhost ip6-loopback
    ff02::1         ip6-allnodes
    ff02::2         ip6-allrouters
    Needs confirming, but may be a gotcha for jessies?
    Last edited by Oblivian; 2018-01-24 at 10:59.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  9. #49
    Passenger
    Join Date
    Jun 2016
    Location
    Mayo Ireland
    Posts
    4
    Quote Originally Posted by vinnyspb View Post
    Additionally to what Oblivian suggested, it would be very helpful to get output of the following commands please:

    cat /etc/default/dump1090-mutability

    fr24feed --version

    cat /var/log/fr24feed/fr24feed.log

    cat /dev/shm/decoder.txt

    ls -al /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt /run/dump1090-mutability

    ps aufx | grep -e fr24 -e dump1090

    sudo systemctl status fr24feed

    sudo grep -e fr24feed -e dump1090 /var/log/syslog
    cat: /etc/default/dump1090-mutability: No such file or directory

    1.0.19-6

    cat: /var/log/fr24feed/fr24feed.log: No such file or directory

    ac_map_size=3072
    build_arch=static_arm
    build_flavour=generic
    build_os=Linux
    build_revision=HEAD-635eb0b.git
    build_timetamp=Jan 23 2018 08:17:49
    build_version=1.0.19-6
    cfg_baudrate=
    cfg_bs=yes
    cfg_host=
    cfg_mpx=no
    cfg_path=
    cfg_raw=yes
    cfg_receiver=dvbt
    cfg_windowmode=0
    d11_map_size=0
    feed_alias=T-EIKN3
    feed_configured_mode=UDP
    feed_current_mode=UDP
    feed_current_server=83.140.21.87
    feed_last_attempt_time=1516794575
    feed_last_config_attempt=1516794575
    feed_last_config_info=
    feed_last_config_result=success
    feed_last_connected_time=1516794575
    feed_status=connected
    feed_status_message=
    fr24key=bd66fb03752584ad
    last_json_utc=1516794781
    last_rx_connect_status=OK
    last_rx_connect_time=1516794852
    last_rx_connect_time_s=2018-01-24 11:54:06


    pi 21925 0.0 0.3 2668 1376 pts/1 S+ 11:56 0:00 \_ grep --color=auto -e fr2 -e dump1090
    root 19340 0.0 0.5 4600 2600 ? S 09:42 0:00 sudo fr24feed
    root 19347 0.1 1.3 106724 5812 ? Sl 09:42 0:12 \_ fr24feed
    nobody 21491 0.1 0.7 106724 3500 ? Ssl 11:49 0:00 /usr/bin/fr24feed




    mlat-ok=NO
    mlat-started=YES
    mlat_problem=no-config
    msg_ring_full=0
    msg_ring_length=0
    offline-mode=no
    rx_connected=0
    shutdown=no
    time_update_utc=1516794823
    time_update_utc_s=2018-01-24 11:53:43
    timing_is_valid=1
    timing_last_drift=-0.0011
    timing_last_offset=-0.0011
    timing_last_result=success
    timing_source=NTP
    timing_time_last_attempt=1516794575
    timing_time_last_success=1516794575
    timing_time_since_last_success=1516794575

    -rw-r--r-- 1 nobody nogroup 1162 Jan 24 11:55 /dev/shm/decoder.txt

    /run/dump1090-mutability:
    total 0
    drwxrwxrwx 2 root root 40 Jan 24 07:05 .
    drwxr-xr-x 19 root root 640 Jan 24 07:05 ..

    /run/fr24feed:
    total 0
    drwxr-xr-x 2 nobody nogroup 40 Jan 24 07:05 .
    drwxr-xr-x 19 root root 640 Jan 24 07:05 ..

    /var/log/fr24feed:
    total 0
    drwxr-xr-x 2 nobody nogroup 40 Jan 24 07:05 .
    drwxr-xr-x 5 root root 280 Jan 24 07:05 ..


    Jan 23 15:27:15 raspberrypi fr24feed[514]: Starting FR24 feeder: fr24feed.
    Jan 24 07:00:01 raspberrypi CRON[16472]: (root) CMD (/usr/lib/fr24/fr24feed_updater.sh >/dev/null 2>&1)
    Jan 24 07:03:23 raspberrypi fr24feed[16546]: Stopping FR24 feeder: fr24feed.
    Jan 24 07:05:47 raspberrypi systemd[1]: fr24feed.service start-pre operation timed out. Terminating.
    Jan 24 07:05:47 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
    Jan 24 07:05:47 raspberrypi systemd[1]: fr24feed.service holdoff time over, scheduling restart.
    Jan 24 07:07:18 raspberrypi systemd[1]: fr24feed.service start-pre operation timed out. Terminating.
    Jan 24 07:07:18 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
    Jan 24 07:07:18 raspberrypi systemd[1]: fr24feed.service holdoff time over, scheduling restart.
    Jan 24 07:08:48 raspberrypi systemd[1]: fr24feed.service start-pre operation timed out. Terminating.
    Jan 24 07:08:49 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
    Jan 24 07:08:49 raspberrypi systemd[1]: fr24feed.service holdoff time over, scheduling restart.

  10. #50
    Flight attendant
    Join Date
    Jun 2015
    Posts
    62
    Looks like you've missed one command:

    sudo systemctl status fr24feed
    Also could you please execute these:

    ls -al /usr/lib/fr24

    cat /etc/fr24feed.ini | grep -v fr24key

    /usr/lib/fr24/dump1090 --help 2>&1 | grep dump1090

Posting Permissions

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