Announcement

Collapse
No announcement yet.

"sudo service fr24feed status" - returns different result - PiZero

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

  • geekycow
    replied
    Additionally, for a low CPU-load dump of the current status-

    Code:
    pi@pollypi:~ $ cat /dev/shm/fr24feed.txt
    Which gives you something like-
    Code:
    ac_map_size=3072
    build_arch=static_arm
    build_flavour=generic
    build_os=Linux
    build_revision=T201704200925
    build_timetamp=Apr 20 2017 09:25:30
    build_version=1.0.18-9
    cfg_baudrate=
    cfg_bs=no
    cfg_host=
    cfg_mpx=no
    cfg_path=/usr/lib/fr24/dump1090
    cfg_raw=no
    cfg_receiver=dvbt
    cfg_windowmode=0
    d11_map_size=25
    feed_alias=T-EGNX82
    feed_configured_mode=UDP
    feed_current_mode=UDP
    feed_current_server=83.140.21.85
    feed_last_ac_sent_num=0
    feed_last_ac_sent_time=1499348559
    feed_last_attempt_time=1499298403
    feed_last_config_attempt=1499298402
    feed_last_config_info=
    feed_last_config_result=success
    feed_last_connected_time=1499298403
    feed_num_ac_tracked=18
    feed_status=connected
    feed_status_message=
    fr24key=[withheld]
    gps_tods=0
    last_json_utc=1499348497
    last_rx_connect_status=OK
    last_rx_connect_time=1499298331
    last_rx_connect_time_s=2017-07-05 23:45:31
    local_tods=49349
    mlat-mode=UDP
    mlat-number-seen=18
    mlat-ok=YES
    mlat-started=YES
    mlat-time-last-ping=1499348555
    mlat-time-last-push=1499348560
    mlat-time-last-push_count=2
    mlat-time-last-seen=1499348557
    mlat-time-stats=1499348560
    mlat-uplink-stats=0
    mlat_problem=no-config
    msg_ring_full=0
    msg_ring_length=0
    num_messages=2724753
    num_resyncs=0
    offline-mode=no
    rx_connected=1
    shutdown=no
    time_update_utc=1499348544
    time_update_utc_s=2017-07-06 13:42:24
    timing_is_valid=1
    timing_last_drift=+0.0018
    timing_last_offset=+0.0020
    timing_last_result=success
    timing_source=NTP
    timing_time_last_attempt=1499348416
    timing_time_last_success=1499348416
    timing_time_since_last_success=629
    Hope that helps?

    Warm Regards
    Julie

    Leave a comment:


  • tsutton
    replied
    JohnnyBravo - the addition of diagnostics in the code did the trick - thanks!

    PHP Code:
    ok FR24 Feeder/Decoder Processrunning.
    ok FR24 Stats Timestamp2016-05-13 19:29:22.
    ok FR24 Linkconnected [UDP].
    ok FR24 RadarT-EGSH27.
    ok FR24 Tracked AC6.
    ok Receiverconnected (1167481 MSGS/0 SYNC).
    ok FR24 MLATok [UDP].
    ok FR24 MLAT AC seen6. 

    Leave a comment:


  • mrcarlos
    replied
    Originally posted by JohnnyBravo View Post
    If you're interested in getting the stats via command line you can edit the file /etc/init.d/fr24feed

    Command would be: sudo /etc/init.d/fr24feed

    At the bottom of the file look for the section that looks like this:

    case "$1" in
    start)
    start
    ;;
    stop)
    stop
    ;;
    status)
    status
    ;;
    restart)
    stop && sleep 2 && start
    ;;
    reload)
    exit 3
    ;;
    status|get_status)
    status_of_proc $DAEMON "fr24feed server"
    ;;
    *)
    echo "Usage: $0 {start|stop|restart|status}"
    exit 2
    ;;
    esac

    And change that to:

    case "$1" in
    start)
    start
    ;;
    stop)
    stop
    ;;
    status|diagnostics)
    status
    ;;
    restart)
    stop && sleep 2 && start
    ;;
    reload)
    exit 3
    ;;
    status|get_status)
    status_of_proc $DAEMON "fr24feed server"
    ;;
    *)
    echo "Usage: $0 {start|stop|restart|status|diagnostics}"
    exit 2
    ;;
    esac

    Exit with CTRL-X, say 'YES' when asked to save the file and just hit enter when asked for the filename.
    Note that the only change is the word 'diagnostics' is added in 2 places.

    You can now run "sudo service fr24feed diagnostics" from the command line and the output will be as you would see on Jessie.
    Wheezy will catch the status request of a service so it won't actually be passed to the init script, so we have to use a different word.
    The above example uses diagnostics as that kinda makes sense, but you can choose any other word...

    Found the above info elsewhere on the forum a while ago, so credits to the original poster (just can't remember who that was).
    big thanks 👍

    Sent from my SM-N910F using Tapatalk

    Leave a comment:


  • G8VXY
    replied
    Originally posted by tsutton View Post
    Ah, OK. That might be why. Thank you.

    Does my result above states that everything are OK?
    Yes mine is feeding and the same quire returns basically the same return.

    From another computer enter in your web browser the ip address of the Raspberry Pi followed with :8754 i.e. "192.168.0.10:8754"

    And you should get somthing like this:

    Screenshot 2016-04-23 13.14.18.jpg

    If Aircraft tracked and Aircraft Uploaded are greater than zero you system is working.

    P.S.
    Some lines were ellipsized
    Means the text lines are to long for the text viewer and the latter part of the text is omitted, these lines end in ...
    If this is a problem expand the size of the text viewer or run it full screen.
    Last edited by G8VXY; 2016-04-23, 12:38.

    Leave a comment:


  • JohnnyBravo
    replied
    If you're interested in getting the stats via command line you can edit the file /etc/init.d/fr24feed

    Command would be: sudo nano /etc/init.d/fr24feed

    At the bottom of the file look for the section that looks like this:

    case "$1" in
    start)
    start
    ;;
    stop)
    stop
    ;;
    status)
    status
    ;;
    restart)
    stop && sleep 2 && start
    ;;
    reload)
    exit 3
    ;;
    status|get_status)
    status_of_proc $DAEMON "fr24feed server"
    ;;
    *)
    echo "Usage: $0 {start|stop|restart|status}"
    exit 2
    ;;
    esac

    And change that to:

    case "$1" in
    start)
    start
    ;;
    stop)
    stop
    ;;
    status|diagnostics)
    status
    ;;
    restart)
    stop && sleep 2 && start
    ;;
    reload)
    exit 3
    ;;
    status|get_status)
    status_of_proc $DAEMON "fr24feed server"
    ;;
    *)
    echo "Usage: $0 {start|stop|restart|status|diagnostics}"
    exit 2
    ;;
    esac

    Exit with CTRL-X, say 'YES' when asked to save the file and just hit enter when asked for the filename.
    Note that the only change is the word 'diagnostics' is added in 2 places.

    You can now run "sudo service fr24feed diagnostics" from the command line and the output will be as you would see on Jessie.
    Wheezy will catch the status request of a service so it won't actually be passed to the init script, so we have to use a different word.
    The above example uses diagnostics as that kinda makes sense, but you can choose any other word...

    Found the above info elsewhere on the forum a while ago, so credits to the original poster (just can't remember who that was).
    Last edited by JohnnyBravo; 2016-05-08, 19:12. Reason: typo

    Leave a comment:


  • tsutton
    replied
    Ah, OK. That might be why. Thank you.

    Does my result above states that everything are OK?

    Leave a comment:


  • Oblivian
    replied
    Wheezy vs jessie displays the service command differently. They are working on a future change, but using the web status gives the required info

    Sent from my XT1092 using Tapatalk

    Leave a comment:


  • "sudo service fr24feed status" - returns different result - PiZero

    Hi all,

    Followed the steps at https://www.flightradar24.com/build-your-own and have it up & running, sharing data to FR24 without issue.

    I ran this command -
    Code:
     sudo service fr24feed status
    but instead of seeing the [OK] listing, I am actually seeing this:

    Code:
    pi@raspberrypi:/ $ sudo service fr24feed status
    ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
       Loaded: loaded (/etc/init.d/fr24feed)
       Active: active (running) since Fri 2016-04-22 20:04:20 UTC; 15min ago
      Process: 2059 ExecStop=/etc/init.d/fr24feed stop (code=exited, status=0/SUCCESS)
      Process: 2105 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/fr24feed.service
               ├─2121 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt -...
               └─2287 /usr/lib/fr24/dump1090 --net-http-port 8080 --raw --mlat
    
    Apr 22 20:04:20 raspberrypi fr24feed[2105]: Starting FR24 feeder: fr24feed.
    Apr 22 20:04:20 raspberrypi systemd[1]: Started LSB: Flightradar24 Decoder &....
    Hint: Some lines were ellipsized, use -l to show in full.
    I have restarted the service (even rebooted the Pi!) but it's still coming back with the same result.

    What am I missing?

    Thanks.
Working...
X