Announcement

Collapse
No announcement yet.

Why did my feeder stop working and won't start again?

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

  • Why did my feeder stop working and won't start again?

    Hello,

    my feeder was running for months without any problems. But now it won't start anymore, although I did not change anything on it. Do you see, where is the problem? How may I get it to run again?



    Code:
    error | Local time: 2022-01-08 16:25:31 +0100
    error | GMT+0 time: 2022-01-08 15:25:31 +0100
    error | Your machine should be set as GMT+0 time zone!
    warning | Time zone is not set to GMT+0
    2022-01-08 16:25:31 | ______ _ _ _ _ _ _____ ___
    2022-01-08 16:25:31 | | ___|| |(_) | | | | | | / __ \ / |
    2022-01-08 16:25:31 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
    2022-01-08 16:25:31 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
    2022-01-08 16:25:31 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
    2022-01-08 16:25:31 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
    2022-01-08 16:25:31 | __/ |
    2022-01-08 16:25:31 | |___/
    2022-01-08 16:25:31 | [main][i]FR24 Feeder/Decoder
    2022-01-08 16:25:31 | [main][i]Version: 1.0.25-3/generic
    2022-01-08 16:25:31 | [main][i]Built on Apr 8 2020 07:00:11 (HEAD-5e8ef0c.git/Linux/static_amd64)
    2022-01-08 16:25:31 | [main][i]Running on: debian11
    2022-01-08 16:25:31 | [main][i]Local IP(s): 192.168.1.7
    2022-01-08 16:25:31 | [main][i]Copyright 2012-2020 Flightradar24 AB
    2022-01-08 16:25:31 | [main][i]https://www.flightradar24.com
    2022-01-08 16:25:31 | [main][i]DNS mode: PING
    2022-01-08 16:25:31 | [main][i]Automatic updates are ENABLED
    2022-01-08 16:25:31 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
    2022-01-08 16:25:31 | info | [httpd]Server started, listening on 0.0.0.0:8754
    2022-01-08 16:25:31 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
    2022-01-08 16:25:31 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
    2022-01-08 16:25:31 | [main][i]Reader thread started
    2022-01-08 16:25:31 | [master][i]Starting processing thread
    2022-01-08 16:25:31 | [time][i]Synchronizing time via NTP
    2022-01-08 16:25:31 | [reader][i]Initializing reader
    2022-01-08 16:25:31 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat 48.3105 --lon 14.2799 --raw)
    2022-01-08 16:25:31 | [reader][i]Connected to the receiver, configuring
    2022-01-08 16:25:31 | [reader][i]Configured, processing messages
    2022-01-08 16:25:31 | [reader][i]Connection terminated
    2022-01-08 16:25:31 | [main][i]Terminating child process 1547 with SIGTERM
    2022-01-08 16:25:32 | [time][i]Time synchronized correctly, offset -0.003 seconds
    2022-01-08 16:25:32 | [main][i]Feed Network client started
    2022-01-08 16:25:32 | [feed][i]Downloading configuration
    2022-01-08 16:25:32 | [feed][d]fetching configuration
    2022-01-08 16:25:32 | [feed][i]configuring decoder
    2022-01-08 16:25:32 | [feed][c]Max range AIR: 350.0nm
    2022-01-08 16:25:32 | [feed][c]Max range GND: 100.0nm
    2022-01-08 16:25:32 | [feed][i]configuration changed
    2022-01-08 16:25:32 | [feed][i]defined 3 servers
    2022-01-08 16:25:32 | [feed][c]Timestamps: optional
    2022-01-08 16:25:32 | info | Stopping ReceiverACSender threads for feed
    2022-01-08 16:25:32 | info | [stats]Stats thread started
    2022-01-08 16:25:32 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: LOWL177, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
    2022-01-08 16:25:32 | info | Network thread connecting to 185.218.24.22:8099 for feed LOWL177
    2022-01-08 16:25:32 | [feed][n]LOWL177@185.218.24.22:8099/UDP
    2022-01-08 16:25:32 | [feed][n]connecting
    2022-01-08 16:25:32 | [feed][n]connected via UDP (fd 28)
    2022-01-08 16:25:32 | [feed][i]Feed connected
    2022-01-08 16:25:32 | [feed][n]working
    2022-01-08 16:25:37 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat 48.3105 --lon 14.2799 --raw)
    2022-01-08 16:25:37 | [reader][i]Connected to the receiver, configuring
    2022-01-08 16:25:37 | [reader][i]Configured, processing messages
    2022-01-08 16:25:37 | [reader][i]Connection terminated
    2022-01-08 16:25:37 | [main][i]Terminating child process 1555 with SIGTERM
    2022-01-08 16:25:42 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat 48.3105 --lon 14.2799 --raw)
    2022-01-08 16:25:42 | [reader][i]Connected to the receiver, configuring
    2022-01-08 16:25:42 | [reader][i]Configured, processing messages
    2022-01-08 16:25:42 | [reader][i]Connection terminated
    2022-01-08 16:25:42 | [main][i]Terminating child process 1563 with SIGTERM
    2022-01-08 16:25:48 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat 48.3105 --lon 14.2799 --raw)

  • #2
    Hello mensa, this looks like a not connected USB DVBT device. Perhaps you have connected the USB DVBT receiver to a different port then USB0 ?
    It happend to me some day, when I was in a hurry.
    Otherwise the DVBT receiver could be defect - check the temperatur of the device, they get quite warm.

    Comment


    • #3
      The DVB-T stick is connected to the same port.
      Which command can verify that?

      Comment


      • #4
        You can verify the status of the receiver looking at Port 8754 using your browser. http://192.xxx.xxx.xxx:8754

        The screen will refresh every ten secon
        ds and show the status.
        Last edited by DJ1MV; 2022-01-10, 14:25.

        Comment


        • #5
          I am searching for a command to list the USB devices. I know that the receiver is currently having troubles, that shows also fr24feed-status command.

          Comment


          • #6
            use lsusb or lspci, I am not familiar with this linux version .. sorry!

            Comment


            • #7
              Thx, so the DVB-T stick can't be defective, as the command lsusb lists it:

              Code:
              root@Server:~# lsusb
              Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
              Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
              Bus 002 Device 002: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
              Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
              Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
              Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

              Comment


              • #8
                Good so far! Is there any other helpful information in the feeder info on port 8754? It should show, that DVBT stick is connected.

                Comment


                • #9
                  Screenshot.jpg

                  Comment


                  • #10
                    It looks like that:


                    pojXSCV.png

                    J16K85u.png


                    Comment


                    • #11

                      ​​​​​This
                      Connecting to receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat 48.3105 --lon 14.2799 --raw)

                      Is not able to start dump1090. So is constantly retrying to. You need to find out why.

                      If you haven't done a full reboot. Fr24.crashed, dump1090 is still/already running and cant start it again using that command cause the USB is locked

                      If you added more feeders. Those have now started their own copy first And you're configured wrong.

                      https://forum.flightradar24.com/foru...427#post210427


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

                      Comment


                      • #12
                        Yes, I rebooted already a lot of times. I did not add more feeders, I have only one.

                        How may I find out now, why it is not starting please?

                        Comment


                        • #13
                          Originally posted by mensa View Post
                          Yes, I rebooted already a lot of times. I did not add more feeders, I have only one.

                          How may I find out now, why it is not starting please?
                          Issue these commands, and post output of last command:
                          Code:
                           
                          sudo apt-get install rtl-sdr  
                          
                          sudo systemctl stop fr24feed  
                          
                          rtl_test -t

                          Comment


                          • #14
                            This is the output:

                            Code:
                            root@Server:~# apt-get install rtl-sdr
                            Reading package lists... Done
                            Building dependency tree... Done
                            Reading state information... Done
                            rtl-sdr is already the newest version (0.6.0-3).
                            The following package was automatically installed and is no longer required:
                            linux-image-4.19.0-18-amd64
                            Use 'apt autoremove' to remove it.
                            0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
                            root@Server:~# systemctl stop fr24feed
                            root@Server:~# rtl_test -t
                            Found 1 device(s):
                            0: Realtek, RTL2838UHIDIR, SN: 00000001
                            
                            Using device 0: Generic RTL2832U OEM
                            Found Rafael Micro R820T tuner
                            Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
                            [R82XX] PLL not locked!
                            Sampling at 2048000 S/s.
                            No E4000 tuner found, aborting.

                            Comment


                            • #15
                              I still have no solution, the same seemed to happen to my device today. After several resets and reviewing the log file I finally replaced the DVBT Stick with a new one (nooelec V4) and now it works again. I'll keep an eye on it and report any new info I will find.

                              One thing: the software restart via ssh or the browser interface does not seem to help in my case, it needs a power-on reset. I guess, the power-on state for the DVBT stick is neccessary.
                              Last edited by DJ1MV; 2022-01-12, 18:18.

                              Comment

                              Working...
                              X