Announcement

Collapse
No announcement yet.

dump1090 not working

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

  • dump1090 not working

    Hello,

    I have recently installed the Raspberry Pi flight tracker onto a new Raspberry Pi. However the dump1090 isn't showing up when doing ipaddress/dump1090/gmap.html in a browser.
    I did check if the service is running which it is and I have also done a restart.

    I did have NGINX installed but shut that down to see if there was some interference.

    Anything I can do to know why its stopped working.

  • #2
    which variation of dump1090 are you using ? The FR24 variant or dump1090-FA from Flightaware ?

    Comment


    • #3
      It is the dump1090-mutability one.

      Comment


      • #4
        What are outputs of following commands?

        Code:
        apt-cache policy lighttpd | grep Installed 
        
        apt-cache policy dump1090-mutability | grep Installed

        Comment


        • #5
          Code:
          apt-cache policy lighttpd | grep Installed
          1.4.69-1
          
           apt-cache policy dump1090-mutability | grep Installed
           1.15~20180310.4a16df3+dfsg-8.1

          Comment


          • #6
            Shutting down nginx is not enough. You have to remove it completely so that lighttpd can work

            Code:
            sudo apt purge nginx
            
            sudo apt purge dump1090-mutability
            
            sudo apt purge lighttpd  
            
            sudo rm -rf /etc/lighttpd  
            
            sudo rm -rf /user/share/dump1090-mutability
            ​​​​​​After above cleanup, reboot Pi. This will restart fr24feed, and when it finds dump1090 is missing, it will automatically install dump1090-mutability and lighttpd as dependency of dump1090-mutability. This will take few minutes after reboot of Pi. After few minutes, check status of fr24feed and web page:

            IP/dump1090/gmap.html


            ​​​​​​​.

            Comment


            • #7
              Done that and now getting a `write_locked - missing monitor file pointer` message when typing `sudo fr24feed status`

              Comment

              Working...
              X