Announcement

Collapse
No announcement yet.

How do I install a file?

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

  • #31
    That just confirms the restart bug is better in that ver that people are reporting.

    Still need to refer to logs to see the stop reasons
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #32
      T-CYYZ52
      ​​
      Installed ver 1.0.26-7 yesterday. No outage till now.


      FR24-Beta-26-7.jpg

      Comment


      • #33
        I installed 1.0.26-7 on 10/8 around 1100. Pi ran the rest of that day and until mid afternoon on 10-9 when FR24 and SkyAware stopped 2x. Then system ran the rest of 10-9 and overnight into 10-10 and all is currently running...
        Attached Files

        Comment


        • #34
          Originally posted by Oblivian View Post
          That just confirms the restart bug is better in that ver that people are reporting.

          Still need to refer to logs to see the stop reasons
          How can I access the log??

          Comment


          • #35
            See if running but dump1090 crashed
            sudo fr24feed-status

            Individual Service status check outside if responds as offline
            sudo systemctl status fr24feed
            sudo systemctl status dump1090-mutability (or -fa)

            And if you enable the full logging in fr24feed for a few days...

            cat /var/log/fr24feed.log

            And I believe you had previously installed the journal logs
            https://github.com/wiedehopf/adsb-wi...g-for-fr24feed
            journalctl -u fr24feed --no-pager

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

            Comment


            • #36
              Originally posted by Oblivian View Post
              See if running but dump1090 crashed
              sudo fr24feed-status

              pi@piaware:~ $ ​​​sudo fr24feed-status
              [ ok ] FR24 Feeder/Decoder Process: running.
              [ ok ] FR24 Stats Timestamp: 2020-10-10 10:58:23.
              [ ok ] FR24 Link: connected [UDP].
              [ ok ] FR24 Radar: T-KIAG4.
              [ ok ] FR24 Tracked AC: 33.
              [ ok ] Receiver: connected (7163352 MSGS/0 SYNC).
              [ ok ] FR24 MLAT: ok [UDP].
              [ ok ] FR24 MLAT AC seen: 28.


              Individual Service status check outside if responds as offline
              sudo systemctl status fr24feed
              sudo systemctl status dump1090-mutability (or -fa)

              And if you enable the full logging in fr24feed for a few days...

              cat /var/log/fr24feed.log

              And I believe you had previously installed the journal logs
              https://github.com/wiedehopf/adsb-wi...g-for-fr24feed
              journalctl -u fr24feed --no-pager


              pi@piaware:~ $ journalctl -u fr24feed --no-pager
              -- Logs begin at Fri 2020-10-09 16:57:53 UTC, end at Sat 2020-10-10 10:58:47 UTC. --
              Oct 09 16:58:04 piaware systemd[1]: Starting Flightradar24 Decoder & Feeder...
              Oct 09 16:58:05 piaware systemd[1]: Started Flightradar24 Decoder & Feeder.

              I hope the above is useful...

              Comment


              • #37
                According to the tracert I don't know how the FR24 feed is running bcz doesn't look like the route is intact...

                Tracing route to 185.218.24.22 over a maximum of 30 hops

                1 2 ms 1 ms 1 ms 192.168.0.1
                2 9 ms 39 ms 9 ms 142.254.215.1
                3 26 ms 20 ms 25 ms agg62.ntnwny1702h.northeast.rr.com [24.58.216.213]
                4 11 ms 11 ms 10 ms agg37.lncsnycd02r.northeast.rr.com [24.58.38.106]
                5 20 ms 14 ms 15 ms be29.rochnyei01r.northeast.rr.com [24.58.32.62]
                6 27 ms 28 ms 30 ms bu-ether13.tustca4200w-bcr00.tbone.rr.com [66.109.6.2]
                7 26 ms 42 ms 29 ms 66.109.5.225
                8 26 ms 26 ms 26 ms 0.ae4.pr1.dca10.tbone.rr.com [66.109.1.113]
                9 26 ms 26 ms 25 ms 108.162.217.57
                10 27 ms 26 ms 26 ms 108.162.217.62
                11 * * * Request timed out.
                12 * * * Request timed out.
                13 * * * Request timed out.
                14 * * * Request timed out.
                15 * * * Request timed out.
                16 * * * Request timed out.
                17 * * * Request timed out.
                18 * * * Request timed out.
                19 * * * Request timed out.
                20 * * * Request timed out.
                21 * * * Request timed out.
                22 * * * Request timed out.
                23 * * * Request timed out.
                24 * * * Request timed out.
                25 * * * Request timed out.
                26 * * * Request timed out.
                27 * * * Request timed out.
                28 * * * Request timed out.
                29 * * * Request timed out.
                30 * * * Request timed out.

                Trace complete.

                Comment


                • #38
                  It's the sort of logs and status to check when it's NOT working as expected.

                  Traceroute/Ping is a bit ho-hum these days. Protection, DNS redirections and routers that just don't respond can skew the results.

                  Once you hit 108.162.217.62 - that is in Cloudflare domain. So starts to get difficult
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment


                  • #39
                    Ok got it. Thank you for explanations.....

                    Comment


                    • #40
                      I just stopped again......


                      pi@piaware:~ $ fr24feed-status
                      [ ok ] FR24 Feeder/Decoder Process: running.
                      [ ok ] FR24 Stats Timestamp:.
                      [FAIL] FR24 Link: unknown ... failed!
                      [ ok ] Receiver: connected (232976 MSGS/0 SYNC).
                      [FAIL] FR24 MLAT: not running ... failed!

                      pi@piaware:~ $ journalctl -u fr24feed --no-pager
                      -- Logs begin at Fri 2020-10-09 16:57:53 UTC, end at Sat 2020-10-10 12:08:40 UTC. --
                      Oct 09 16:58:04 piaware systemd[1]: Starting Flightradar24 Decoder & Feeder...
                      Oct 09 16:58:05 piaware systemd[1]: Started Flightradar24 Decoder & Feeder.
                      Oct 10 11:42:44 piaware systemd[1]: fr24feed.service: Main process exited, code=killed, status=6/ABRT
                      Oct 10 11:42:44 piaware systemd[1]: fr24feed.service: Failed with result 'signal'.
                      Oct 10 11:42:44 piaware systemd[1]: fr24feed.service: Service RestartSec=100ms expired, scheduling restart.
                      Oct 10 11:42:44 piaware systemd[1]: fr24feed.service: Scheduled restart job, restart counter is at 1.
                      Oct 10 11:42:44 piaware systemd[1]: Stopped Flightradar24 Decoder & Feeder.
                      Oct 10 11:42:44 piaware systemd[1]: Starting Flightradar24 Decoder & Feeder...
                      Oct 10 11:42:44 piaware systemd[1]: Started Flightradar24 Decoder & Feeder.


                      pi@piaware:~ $ sudo systemctl status fr24feed
                      ● fr24feed.service - Flightradar24 Decoder & Feeder
                      Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
                      Active: active (running) since Sat 2020-10-10 11:42:44 UTC; 31min ago
                      Process: 26811 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
                      Process: 26815 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
                      Process: 26820 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=0/SUCCESS)
                      Main PID: 26823 (fr24feed)
                      Tasks: 16 (limit: 2200)
                      Memory: 5.9M
                      CGroup: /system.slice/fr24feed.service
                      └─26823 /usr/bin/fr24feed

                      Oct 10 11:42:44 piaware systemd[1]: Starting Flightradar24 Decoder & Feeder...
                      Oct 10 11:42:44 piaware systemd[1]: Started Flightradar24 Decoder & Feeder.


                      pi@piaware:~ $ sudo systemctl status dump1090-mutability (or -fa)
                      -bash: syntax error near unexpected token `('

                      Comment


                      • #41
                        I hope you don't have it configured as 'dvbt' receiver still?

                        Because piaware base means it should be beast-tcp, 127.0.0.1:30005

                        Oct 10 11:42:44 piaware systemd[1]: fr24feed.service: Failed with result 'signal

                        No signal/aircraft at that time?

                        Because fr24 is running. But it's not seeing data...

                        Active: active (running) since Sat 2020-10-10 11:42:44 UTC; 31min ago

                        Last command isn't a copy paste, it's s pick one. The -fa meant if you have dump1090-fa, put that instead of mutability as the name

                        Piaware, will be
                        Sudo systemctl status dump1090-fa
                        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                        Comment


                        • #42
                          Its configured as beast-tcp, 127.0.0.1:30005
                          And yes, I realized my mistake in not picking one or the other !

                          I did a restart via the FlightAware console and back running...

                          Comment


                          • #43

                            It is now almost 48 hours since I installed version 1.0.26-7.
                            Going Strong



                            FR24-26-7-b.png

                            Comment


                            • #44
                              That sounds like dump 1090-fa is going offline if restarting its service works.

                              Which will also stop json/local map updates.

                              (But the connectors can remain taking to server. )

                              How is the usb connected. Straight in, exrension cable, and is it powered by usb or a 2A power pack (they can go bad)

                              Hope through these individual tests you're getting an understanding how there are many components/steps to feeding with a dvbt, and restarting pi can mask true causes of outtages

                              ... Also shows I'm not pulling people's leg that get angry at me when I advise a few extra commands to dig deeper that are after a quick fix :/

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

                              Comment


                              • #45
                                ADDED:

                                OPTION 2 - Using WinSCP:

                                https://forum.flightradar24.com/foru...214#post194214

                                When tried to save the edited post, this stupid forum declared it spam and I got this message:
                                "This post has been declared a potential spam, and wont be visible unless approved by a moderator."

                                Oblivian:
                                Can you please approve it? Thanks

                                LATER ADDITION:
                                Thank you Oblivian, it is visible now.
                                .
                                Last edited by abcd567; 2020-10-11, 03:02.

                                Comment

                                Working...
                                X