Announcement

Collapse
No announcement yet.

Two feeds in the same Raspberry

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

  • #16
    Thanks for helping me as well!


    Here the output: (part 1)

    pi@raspberrypi:~ $ sudo systemctl restart lighttpd
    Job for lighttpd.service failed because the control process exited with error code.
    See "systemctl status lighttpd.service" and "journalctl -xe" for details.
    pi@raspberrypi:~ $ sudo journalctl -u lighttpd --no-pager
    -- Logs begin at Wed 2019-10-23 10:47:37 WEST, end at Wed 2019-10-23 13:37:14 WEST. --
    Oct 23 10:47:42 raspberrypi systemd[1]: Starting Lighttpd Daemon...
    Oct 23 10:47:44 raspberrypi lighttpd[409]: Duplicate array-key '^/dump1090$'
    Oct 23 10:47:44 raspberrypi lighttpd[409]: 2019-10-23 10:47:42: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
    Oct 23 10:47:44 raspberrypi lighttpd[409]: 2019-10-23 10:47:42: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Oct 23 10:47:44 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Oct 23 10:47:44 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Oct 23 10:47:44 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
    Oct 23 10:47:44 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Oct 23 10:47:44 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 1.
    Oct 23 10:47:44 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
    Oct 23 10:47:44 raspberrypi systemd[1]: Starting Lighttpd Daemon...
    Oct 23 10:47:44 raspberrypi lighttpd[569]: Duplicate array-key '^/dump1090$'
    Oct 23 10:47:44 raspberrypi lighttpd[569]: 2019-10-23 10:47:44: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
    Oct 23 10:47:44 raspberrypi lighttpd[569]: 2019-10-23 10:47:44: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Oct 23 10:47:44 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Oct 23 10:47:44 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Oct 23 10:47:44 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
    Oct 23 10:47:45 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Oct 23 10:47:45 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 2.
    Oct 23 10:47:45 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
    Oct 23 10:47:45 raspberrypi systemd[1]: Starting Lighttpd Daemon...
    Oct 23 10:47:45 raspberrypi lighttpd[575]: Duplicate array-key '^/dump1090$'
    Oct 23 10:47:45 raspberrypi lighttpd[575]: 2019-10-23 10:47:45: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
    Oct 23 10:47:45 raspberrypi lighttpd[575]: 2019-10-23 10:47:45: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Oct 23 10:47:45 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Oct 23 10:47:45 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Oct 23 10:47:45 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
    Oct 23 10:47:45 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Oct 23 10:47:45 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 3.
    Oct 23 10:47:45 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
    Oct 23 10:47:45 raspberrypi systemd[1]: Starting Lighttpd Daemon...
    Oct 23 10:47:46 raspberrypi lighttpd[588]: Duplicate array-key '^/dump1090$'
    Oct 23 10:47:46 raspberrypi lighttpd[588]: 2019-10-23 10:47:45: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
    Oct 23 10:47:46 raspberrypi lighttpd[588]: 2019-10-23 10:47:45: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Oct 23 10:47:46 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 4.
    Oct 23 10:47:46 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
    Oct 23 10:47:46 raspberrypi systemd[1]: Starting Lighttpd Daemon...
    Oct 23 10:47:46 raspberrypi lighttpd[617]: Duplicate array-key '^/dump1090$'
    Oct 23 10:47:46 raspberrypi lighttpd[617]: 2019-10-23 10:47:46: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
    Oct 23 10:47:46 raspberrypi lighttpd[617]: 2019-10-23 10:47:46: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Oct 23 10:47:46 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
    Oct 23 10:47:46 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
    Oct 23 10:47:46 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
    Oct 23 10:47:46 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
    Oct 23 13:36:57 raspberrypi systemd[1]: Starting Lighttpd Daemon...
    Oct 23 13:36:57 raspberrypi lighttpd[18903]: Duplicate array-key '^/dump1090$'
    Oct 23 13:36:57 raspberrypi lighttpd[18903]: 2019-10-23 13:36:57: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)



    Originally posted by wiedehopf View Post
    That's some sort of lighttpd issue i'd say.

    Show the output of this:

    sudo systemctl restart lighttpd
    sudo journalctl -u lighttpd --no-pager

    Comment


    • #17
      Output: (part 2)

      Oct 23 13:36:57 raspberrypi lighttpd[18903]: 2019-10-23 13:36:57: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
      Oct 23 13:36:57 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
      Oct 23 13:36:57 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
      Oct 23 13:36:57 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
      Oct 23 13:36:57 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
      Oct 23 13:36:57 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 1.
      Oct 23 13:36:57 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
      Oct 23 13:36:57 raspberrypi systemd[1]: Starting Lighttpd Daemon...
      Oct 23 13:36:58 raspberrypi lighttpd[18911]: Duplicate array-key '^/dump1090$'
      Oct 23 13:36:58 raspberrypi lighttpd[18911]: 2019-10-23 13:36:57: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
      Oct 23 13:36:58 raspberrypi lighttpd[18911]: 2019-10-23 13:36:57: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
      Oct 23 13:36:58 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 2.
      Oct 23 13:36:58 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
      Oct 23 13:36:58 raspberrypi systemd[1]: Starting Lighttpd Daemon...
      Oct 23 13:36:58 raspberrypi lighttpd[18916]: Duplicate array-key '^/dump1090$'
      Oct 23 13:36:58 raspberrypi lighttpd[18916]: 2019-10-23 13:36:58: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
      Oct 23 13:36:58 raspberrypi lighttpd[18916]: 2019-10-23 13:36:58: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
      Oct 23 13:36:58 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
      Oct 23 13:36:58 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 3.
      Oct 23 13:36:58 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
      Oct 23 13:36:58 raspberrypi systemd[1]: Starting Lighttpd Daemon...
      Oct 23 13:36:59 raspberrypi lighttpd[18924]: Duplicate array-key '^/dump1090$'
      Oct 23 13:36:59 raspberrypi lighttpd[18924]: 2019-10-23 13:36:58: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
      Oct 23 13:36:59 raspberrypi lighttpd[18924]: 2019-10-23 13:36:58: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
      Oct 23 13:36:59 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 4.
      Oct 23 13:36:59 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
      Oct 23 13:36:59 raspberrypi systemd[1]: Starting Lighttpd Daemon...
      Oct 23 13:36:59 raspberrypi lighttpd[18929]: Duplicate array-key '^/dump1090$'
      Oct 23 13:36:59 raspberrypi lighttpd[18929]: 2019-10-23 13:36:59: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 10 pos: 10 parser failed somehow near here: (EOL)
      Oct 23 13:36:59 raspberrypi lighttpd[18929]: 2019-10-23 13:36:59: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
      Oct 23 13:36:59 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
      Oct 23 13:36:59 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
      Oct 23 13:36:59 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
      Oct 23 13:36:59 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.

      Comment


      • #18
        sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf
        sudo systemctl restart lighttpd

        The above should fix it, you had dump1090 mutability installed previously which gives problems with the dump1090-fa lighttpd config.

        Comment


        • #19
          It is now fixed, both maps are working!
          Many thanks "wiedehopf" and "abcd567" for all your great support, much appreciated!


          Originally posted by wiedehopf View Post
          sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf
          sudo systemctl restart lighttpd

          The above should fix it, you had dump1090 mutability installed previously which gives problems with the dump1090-fa lighttpd config.

          Comment


          • #20
            Thanks wiedehopf for helping HF_ATL and solving his dump1090 map issue.

            I was sleeping when HF_ATL posted his last few replies (it was late night/early morning in Canada). Just now saw the replies.

            Yesterday HF_ALT has confirmed that both FR24 sites are showing data is being received, and posted screenshots of dump1090 & fr24 config files which showed dump1090 & fr24feed configs are OK. I had then concluded that either it is browser cache problem or lighttpd config issue, but first wanted to make sure it is not the most common browser cache issue.

            Comment


            • #21
              Originally posted by HF_ATL View Post
              I have only one piaware account, I did not configured the other one. My main objective is to have two fr24 feeders but of course I can register for the other email a flightaware account...
              If you dont want to configure and use 2nd piaware feeder, better disable it with following commands, so that it does not unnecessarily keep running in the background.

              Code:
              sudo systemctl stop piaware2
              sudo systemctl disable piaware2

              In future if you decide to have the 2nd piaware also, you can reactivate it by following commands

              Code:
              sudo systemctl enable piaware2
              sudo systemctl start piaware2

              Comment


              • #22
                I have done it now.
                Many thanks for all your help, really much appreciated!

                Originally posted by abcd567 View Post
                If you dont want to configure and use 2nd piaware feeder, better disable it with following commands, so that it does not unnecessarily keep running in the background.

                Code:
                sudo systemctl stop piaware2
                sudo systemctl disable piaware2

                In future if you decide to have the 2nd piaware also, you can reactivate it by following commands

                Code:
                sudo systemctl enable piaware2
                sudo systemctl start piaware2

                Comment


                • #23
                  You can have multiple stations per account on FR24 and FA.

                  But if it's the same location, another station is probably not required.
                  No matter enjoy the upgrade on both accounts i guess

                  Comment


                  • #24
                    Originally posted by wiedehopf View Post
                    You can have multiple stations per account on FR24 and FA.
                    I do have 3 stations under same FR24 account, and 3 stations under same FA account.
                    Two are fed from RPi Model 2B using "1-Pi-2-Receivers", and third one from OrangePiPC using standard single install.


                    Antenna-1 >> dvbt-1 >> dump1090-mutability >> port 30005 >> feeders set #1 to multiple sites.

                    Antenna-2 >> dvbt-2 >> dump1090-mutability2 >> port 31005 >> feeders set #2 to multiple sites.

                    • 2 antennas connected to 2 dongles plugged into single RPi 2B+
                    • 2 instances of dump1090-mutability
                    • 2 instances of piaware (Stn 5252 & 6396)
                    • 2 instances of fr24feed (Stn CYYZ9 & CYYZ21)
                    • 2 instances of pfclient
                    • 2 instances of adsbexchane feeders
                    • 1 instance of rb24feed
                    • 1 instance of opensky-network feeder
                    • 1 instance of wiedehopf’s graphs



                    Originally posted by wiedehopf View Post
                    But if it's the same location, another station is probably not required.
                    If someone has two antennas located on different sides of the house providing different coverage, this arrangement saves the cost of one set of (RPi + Power Supply Adapter + Pi Case + Network Cable).

                    And MLAT still works normally for both FR24 and FA...
                    Last edited by abcd567; 2019-10-23, 21:58.

                    Comment


                    • #25
                      Originally posted by wiedehopf View Post
                      sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf
                      sudo systemctl restart lighttpd

                      The above should fix it, you had dump1090 mutability installed previously which gives problems with the dump1090-fa lighttpd config.
                      Uninstalling dump1090-mutability leaves out lighttpd config saying /etc/lighttpd/conf-enabled cannot be remove as it is not empty. It also sometimes leaves /usr/share/dump1090-mutability/html because it is not empty.

                      For this reason I alwasys tell to issue 2 extra commands after removal/purge command, as shown below:

                      Code:
                      sudo dpkg --purge dump1090-mutability
                      sudo rm -rf /etc/lighttpd
                      sudo rm -rf /usr/share/dump1090-mutability
                      If after above commands, dump1090-fa or dump1090-mut v1.15 is installed, it becomes a clean install without any issues such as faced by HF_ATL
                      .
                      Last edited by abcd567; 2019-10-23, 19:59.

                      Comment


                      • #26
                        Currently the 2-receiver install script is designed to run on a clean fresh install of Raspbian image. It assumes there was no previous install of lighttpd, dump1090 (mut or fa), and piaware.

                        I think I should add following commands at start of install script of the "1 Pi 2 Receivers", so that it removes previous installs of (lighttpd+dump1090-mutability/dump1090-fa) before proceeding to fresh install.

                        Code:
                        sudo dpkg --purge dump1090-mutability
                        sudo apt-get purge dump1090-fa
                        sudo apt-get purge piaware
                        sudo apt-get purge lighttpd
                        sudo rm -rf /etc/lighttpd
                        sudo rm -rf /usr/share/dump1090-mutability
                        sudo rm -rf /usr/share/dump1090-fa
                        Last edited by abcd567; 2019-10-23, 20:42.

                        Comment


                        • #27
                          So do you advise me to run those command lines at this stage?
                          I've run "sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf", "sudo systemctl restart lighttpd" only.
                          And you're right, I had dump1090-mutability before, that's why I got that issue... you really should add those command lines in the step by step tutorial to avoid this issue happening to other users. For anyone who lacks experience in linux environment like me that additional information will make big difference.


                          Originally posted by abcd567 View Post
                          Uninstalling dump1090-mutability leaves out lighttpd config saying /etc/lighttpd/conf-enabled cannot be remove as it is not empty. It also sometimes leaves /usr/share/dump1090-mutability/html because it is not empty.

                          For this reason I alwasys tell to issue 2 extra commands after removal/purge command, as shown below:

                          Code:
                          sudo dpkg --purge dump1090-mutability
                          sudo rm -rf /etc/lighttpd
                          sudo rm -rf /usr/share/dump1090-mutability
                          If after above commands, dump1090-fa or dump1090-mut v1.15 is installed, it becomes a clean install without any issues such as faced by HF_ATL
                          .

                          Comment


                          • #28
                            My situation is that I have two different antennas in different locations on my house. To take the most advantage of covering area I decided to use two FR24 accounts. Otherwise I needed to run two Pi's with more energy wasted for no benefit. This way I can contribute more to FR24 feeding.


                            Originally posted by wiedehopf View Post
                            You can have multiple stations per account on FR24 and FA.

                            But if it's the same location, another station is probably not required.
                            No matter enjoy the upgrade on both accounts i guess

                            Comment


                            • #29
                              Originally posted by HF_ATL View Post
                              you really should add those command lines in the step by step tutorial to avoid this issue happening to other users. For anyone who lacks experience in linux environment like me that additional information will make big difference.
                              Most people don't feel the need to run 2 copies or uninstall dump1090. So it only adds to people running it, without knowing the consequences. And making more of a mess
                              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                              Comment


                              • #30
                                Since there is dump1090 mutability and dump1090fa decoders there can be always some mess.
                                Also not everyone come to a particular thread by the time that they are still in a clean fresh install thus many issues can easily appear for that reason.


                                Originally posted by Oblivian View Post
                                Most people don't feel the need to run 2 copies or uninstall dump1090. So it only adds to people running it, without knowing the consequences. And making more of a mess

                                Comment

                                Working...
                                X