Announcement

Collapse
No announcement yet.

Two feeds in the same Raspberry

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

  • HF_ATL
    replied
    Originally posted by abcd567 View Post
    Sorry, I am sick and cant help right now.
    Will try when recovered
    You've already helped me!
    Thank you for your availability and hope you recover quickly!

    Leave a comment:


  • abcd567
    replied
    Sorry, I am sick and cant help right now.
    Will try when recovered

    Leave a comment:


  • HF_ATL
    replied
    Thank you for the clarification!

    Leave a comment:


  • abcd567
    replied
    Screenshot_20230203_162000_Termux.jpg
    ​​​​​​

    Both copies of fr24feed use same linux binary fr24feed. So both will get upgraded. There is no second binary fr24feed-2


    .

    Leave a comment:


  • HF_ATL
    replied
    Hello again,


    I've received the email from FR24 regarding upgrading to the latest 1.0.34-0 version.
    I've done the upgrade process from the following commands:

    Code:
    sudo chmod +x /usr/lib/fr24/fr24feed_updater.sh
    sudo /usr/lib/fr24/fr24feed_updater.shGeneric
    But since I have two FR24 feeds in the same raspberry PI how can I guarantee that both are updated to the latest version?


    Thank you in advance!

    Leave a comment:


  • HF_ATL
    replied
    Many thanks once more @abcd567

    Now all traces are gone, after reboot and typing those last command lines I got always "...service could not be found"

    Leave a comment:


  • abcd567
    replied
    Originally posted by HF_ATL View Post
    You're right. Better to start from a fresh install and avoid dealing with all of these issues.
    However by this time I'll not do it since it is working despite this issue. So it doesn't really matter

    Btw here is my output:
    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/nginx/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/.debhelper/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/.debhelper/generated/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/usr/share/doc/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/usr/share/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/usr/bin/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/etc/nginx/sites-available/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/etc/init.d/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/etc/logrotate.d/dump1090-mutability
    /run/dump1090-mutability
    find: ‘/run/user/1000/gvfs’: Permission denied
    /etc/nginx/sites-available/dump1090-mutability
    /etc/dump1090-mutability
    /etc/default/dump1090-mutability
    /etc/logrotate.d/dump1090-mutability

    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability2
    find: ‘/run/user/1000/gvfs’: Permission denied

    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability-2
    /usr/share/dump1090-mutability-2
    find: ‘/run/user/1000/gvfs’: Permission denied
    /etc/init.d/dump1090-mutability-2
    /etc/default/dump1090-mutability-2



    First disable the auto start of dump1090-mutability-2 at boot
    Code:
    sudo update-rc.d -f dump1090-mutability-2 remove 
    
    sudo systemctl daemon-reload

    Now remove all left-over garbage of dump1090-mutability/dump1090-mutability-2:
    Code:
    sudo rm -rf /run/dump1090-mutability
    sudo rm /etc/nginx/sites-available/dump1090-mutability
    sudo rm -rf /etc/dump1090-mutability
    sudo rm /etc/default/dump1090-mutability
    sudo rm /etc/logrotate.d/dump1090-mutability
    
    sudo rm -rf /usr/share/dump1090-mutability-2
    sudo rm /etc/init.d/dump1090-mutability-2
    sudo rm /etc/default/dump1090-mutability-2

    Now reboot and check
    Code:
    sudo reboot
    
    sudo systemctl status dump1090-mutability
    sudo systemctl status dump1090-mutability2
    sudo systemctl status dump1090-mutability-2
    
    sudo find / -name dump1090-mutability-2
    Last edited by abcd567; 2019-10-25, 17:08.

    Leave a comment:


  • HF_ATL
    replied
    Originally posted by abcd567 View Post
    HF_ATL:

    Oh, your output of "find" commands show that at some stage you have built dump1090-mutability from source code.

    The 2-receiver script does NOT build from source code. It downloads and installs the pre-built .deb package which I have built and uploaded to Github.
    Yes that makes sense since this system is running for some time and in the past I may have built dump1090-mutability from source code.

    Leave a comment:


  • abcd567
    replied
    HF_ATL:

    Oh, your output of "find" commands show that at some stage you have built dump1090-mutability from source code.

    The 2-receiver script does NOT build from source code. It downloads and installs the pre-built .deb package which I have built and uploaded to Github.
    Last edited by abcd567; 2019-10-25, 13:42.

    Leave a comment:


  • HF_ATL
    replied
    Originally posted by abcd567 View Post
    If HF_ATL has executed commands in my following post, then /etc/init.d/ files will be first disabled (note remove at the end of first 2 commands), then deleted also

    All about feeding data to Flightradar24 (The Flightradar24 receiver, Raspberry Pi and Windows feeding software). No discussions about Flightradar24 web or apps.


    The problem is not due to files generated by script. It is due to files with suffix -2, which are not generated by script, must have been done manually.
    I confirm that I have executed those commands.

    Leave a comment:


  • abcd567
    replied
    Originally posted by wiedehopf View Post
    Wait so it's generating it from the /etc/init.d/ files?
    That makes more sense, must have gotten it backwards.

    I have no clue which file you still have floating around and frankly it doesn't matter because the executable is no longer around.
    If HF_ATL has executed commands in my following post, then /etc/init.d/ files will be first disabled (note remove at the end of first 2 commands), then deleted also

    All about feeding data to Flightradar24 (The Flightradar24 receiver, Raspberry Pi and Windows feeding software). No discussions about Flightradar24 web or apps.


    The problem is not due to files generated by script. It is due to files with suffix -2, which are not generated by script, must have been done manually.
    Last edited by abcd567; 2019-10-25, 13:30.

    Leave a comment:


  • HF_ATL
    replied
    You're right. Better to start from a fresh install and avoid dealing with all of these issues.
    However by this time I'll not do it since it is working despite this issue. So it doesn't really matter

    Btw here is my output:
    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/nginx/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/.debhelper/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/.debhelper/generated/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/usr/share/doc/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/usr/share/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/usr/bin/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/etc/nginx/sites-available/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/etc/init.d/dump1090-mutability
    /home/pi/build-dump-mut/dump1090/debian/dump1090-mutability/etc/logrotate.d/dump1090-mutability
    /run/dump1090-mutability
    find: ‘/run/user/1000/gvfs’: Permission denied
    /etc/nginx/sites-available/dump1090-mutability
    /etc/dump1090-mutability
    /etc/default/dump1090-mutability
    /etc/logrotate.d/dump1090-mutability

    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability2
    find: ‘/run/user/1000/gvfs’: Permission denied

    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability-2
    /usr/share/dump1090-mutability-2
    find: ‘/run/user/1000/gvfs’: Permission denied
    /etc/init.d/dump1090-mutability-2
    /etc/default/dump1090-mutability-2

    Leave a comment:


  • abcd567
    replied
    Running the 2-receiver script for dump1090-fa AFTER re-imaging would have been much better as it wont have any left-over files of dump1090-mutability.

    Leave a comment:


  • abcd567
    replied
    Please note that the 2-receiver script does not generate dump1090-mutability-2, it generates dump1090-mutability2 (ie sufix 2 and not -2). It seems you have done some configuration manually.

    Here is the output on my 2-receiver install, which clearly shows dump1090-mutability-2 does not exist.

    Code:
    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability
    /etc/default/dump1090-mutability
    /etc/nginx/sites-available/dump1090-mutability
    /etc/logrotate.d/dump1090-mutability
    /etc/init.d/dump1090-mutability
    find: ‘/proc/12809’: No such file or directory
    find: ‘/proc/12985’: No such file or directory
    /usr/share/dump1090-mutability
    /usr/share/doc/dump1090-mutability
    /usr/bin/dump1090-mutability
    /run/dump1090-mutability
    
    
    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability2
    /etc/default/dump1090-mutability2
    /etc/init.d/dump1090-mutability2
    /run/dump1090-mutability2
    
    
    pi@raspberrypi:~ $ sudo find / -name dump1090-mutability-2
    pi@raspberrypi:~

    Leave a comment:


  • abcd567
    replied
    You can find left-over files location by command:

    Code:
    sudo find / -name dump1090-mutability
    sudo find / -name dump1090-mutability2
    sudo find / -name dump1090-mutability-2
    Last edited by abcd567; 2019-10-25, 13:08.

    Leave a comment:

Working...
X