No announcement yet.

PI24: Replace dump1090 v1.14 -> pre-build package of dump1090 v1.15

This topic is closed.
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    That explains everything.

    According to FlightAware - MLAT reported:
    v1.14 - 9500 positions per day,
    v1.15 update 24000 positions per day!


    • #32
      Is it possible to replace the FA dump1090 (dump1090-fa) with dump1090 V1.15?

      If yes, what's the most painless way?
      I am using a Pi 3B on Buster, all feeder self installed, so not a preinstalled image like Piaware


      • #33
        There's really no reason to do that. The developer of 1.15 continued the development of 1.15 at FA, so it became dump1090-fa.

        If you want the old interface with dump1090-fa, that's not too hard:


        • #34
          got it, thanks. Never thought that the FA version is it

          I have the retro version already installed beside your TAR version. all works fine


          • #35
            Originally posted by magnum View Post
            Is it possible to replace the FA dump1090 (dump1090-fa) with dump1090 V1.15?

            If yes, what's the most painless way?
            I am using a Pi 3B on Buster, all feeder self installed, so not a preinstalled image like Piaware
            It is good if you followed instructions/advise by wiedehopf.

            However just co complete records, the most painless way to replce dump1090-fa by dump1090-mutability ver 1.15 on Buster is as follows:

            sudo systemctl stop piaware
            sudo systemctl stop dump1090-fa
            sudo apt-get purge dump1090-fa
            sudo rm -rf /etc/lighttpd
            sudo apt-get update
            sudo apt-get install lighttpd
            sudo apt-get install dump1090-mutability
            sudo wget -O /etc/udev/rules.d/rtl-sdr.rules "" 
            sudo reboot


            • #36
              That probably will result in problems as not all lighttpd files are installed correctly.
              If you do the rm -rf, you should also purge lighttpd.
              That way all configuration files will be created when installing lighttpd after that.

              If lighttpd was installed before, the package system doesn't "know" you deleted the lighttpd configuration files and won't write them when installing it.
              Without configuration files it won't work.

              It probably would be a better idea to only delete dump1090-fa related lighttpd configuration files like this:

              sudo rm -f /etc/lighttpd/conf-enabled/*dump1090-fa*

              Also you don't know what else might be installed which the user might want retained (graphs, .... etc)
              Last edited by wiedehopf; 2019-09-04, 19:55.


              • #37
                Thanks, but after the reply of wiedehopf earlier i leave my setup as it is.


                • #38
                  When installing dump1090-fa by package install as per following page, then lighttpd gets installed automatically as dependency of dump1090-fa.


                  Consequently purging dump1090-fa purges lighttpd also, but for some reason leaves out folder /etc/lighttpd/.

                  If someone tries to remove/purge lighttpd before removing/purging dump1090-fa, system refuses telling it cannot be removed as dump1090-fa depends on it. If tried to purge after purging dump1090-fa, system tells it cant remove/purge lighttpd as it does not exist.

                  Even if lighttpd is installed independently, and if afterwards it is removed by purge command, the folder /etc/lighttpd does NOT get removed for unknown reason.

                  It needs to be removed manually.
                  Last edited by abcd567; 2019-09-04, 20:42.


                  • #39
                    Purging dump1090-fa will not purge its dependencies like lighttpd.
                    (Lighttpd will be auto-removed when issuing the auto-remove command. But it won't delete the lighttpd config files)

                    What happens though when purging dump1090-fa, the config files in conf-available get deleted while the symlinks sometimes remain in conf-enabled, thus preventing lighttpd from starting.
                    So i'm not against solving that issue.

                    Remove only the relevant files (stuff in conf-enabled), it's the better approach.

                    You can issue this command:
                    sudo apt purge dump1090-fa lighttpd

                    This will work because at this point both are installed.


                    • #40
                      Trying to learn more;

                      I think I have lost a file which should be in /etc/lighttpd, there is only a folder conf-available

                      so mypiip/dump1090 does not load now (data is still working)

                      Now I am thinking of trying to remove /etc/lighttpd, purge lighttpd and install again.
                      Last edited by Gomac; 2019-09-06, 07:39. Reason: correction


                      • #41
                        sudo apt install lighttpd
                        sudo apt purge lighttpd
                        sudo apt install lighttpd

                        At this point you might need to purge and reinstall your dump1090 version as well.

                        sudo lighty-enable-mod dump1090

                        Deleting the whole /etc/lighttpd directory is a really bad idea.


                        • #42
                          Thank you for your help, I now have 404 - not found at piip/dump1090
                          Last edited by Gomac; 2019-09-06, 08:17. Reason: typo


                          • #43
                            sudo dpkg --purge dump1090-mutability
                            cd /usr/lib/fr24/ 
                            sudo ./ 
                            sudo service lighttpd force-reload 
                            sudo systemctl restart fr24feed


                            • #44
                              Working again thank you all for your help. Now I must try some of the other gadgets, which means I will probably break it again ;-)


                              • #45
                                So far I just run the automatic script to update from 1.14 to 1.15 but without success.

                                What I see is that dumo1090-mutability is not installed.

                                At the end of the process I give: service fr24feed status and this is what I get:

                                service fr24feed status
                                ● fr24feed.service - Flightradar24 Decoder & Feeder
                                Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled)
                                Active: active (running) since Wed 2019-09-18 16:50:07 CEST; 1min 56s ago
                                Process: 1549 ExecStartPre=/usr/lib/fr24/ (code=exited, status=0/SUCCESS)
                                Process: 1544 ExecStartPre=/usr/lib/fr24/ (code=exited, status=0/SUCCESS)
                                Process: 1509 ExecStartPre=/usr/lib/fr24/ (code=exited, status=100)
                                Main PID: 1553 (fr24feed)
                                CGroup: /system.slice/fr24feed.service
                                └─1553 /usr/bin/fr24feed

                                Sep 18 16:50:07 orangepipcplus systemd[1]: Started Flightradar24 Decoder & Feeder.

                                there is no /usr/bin/dump1090-mutability file right now.

                                I am getting few error messages while running the script starting from here:

                                Get:53 jessie/main armhf Packages [178 B]
                                Err jessie/main armhf Packages

                                Get:54 jessie/utils armhf Packages [178 B]
                                Err jessie/utils armhf Packages

                                Get:55 jessie/jessie-desktop armhf Packages [178 B]
                                Err jessie/jessie-desktop armhf Packages

                                W: There is no public key available for the following key IDs:
                                W: Failed to fetch HttpError404

                                W: Failed to fetch HttpError404

                                W: Failed to fetch HttpError404

                                W: Failed to fetch 404 Not Found [IP: 80]

                                .and more

                                What do you think about it ?

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