Two feeds in the same Raspberry

[wiedehopf]

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.

[abcd567]

The dump1090-mutability's service file is generated by the system (systemd-sysv-generator) at boot from its init.d file "/etc/init.d/dump1090-mutability". The last set of commands I gave should remove this file for both instances. It must be left-over copy of service file which can be removed by command mentioned by weidehopf

sudo rm -f /lib/systemd/system/dump1090-mutability.service /etc/systemd/system/dump1090-mutability.service 

sudo reboot

You can find left-over file location by command:

sudo find / -name dump1090-mutability

After this headache, do you realize it was better to re-image and then install dump1090-fa?

[wiedehopf]

That's a 2nd service you must have created yourself. (note the -2)

Remove it like this.

sudo rm -f /lib/systemd/system/dump1090-mutability-2.service /etc/systemd/system/dump1090-mutability-2.service
sudo reboot

Removing the displayed file in init.d didn't help because it's generated from the service file.

If you don't know what you are doing and have followed one guide unsuccessfully and don't know how to undo what you did, it's really best to start with a fresh image.

[HF_ATL]

That's not running:


But if you mind it we can remove the service files and it should be gone:

sudo rm -f /lib/systemd/system/dump1090-mutability.service /etc/systemd/system/dump1090-mutability.service
sudo reboot

Anyway the snippet you showed just shows that it was running 2 days ago, not that it's running.
So it doesn't really matter.

Now I have the following output for the "sudo systemctl status dump1090-mutability":
dump1090_mut.png

[wiedehopf]

That's not running:

dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
Loaded: loaded (/etc/init.d/dump1090-mutability; generated)
Active: active (exited) since Wed 2019-10-23 14:10:49 WEST; 1 day 18h ago

But if you mind it we can remove the service files and it should be gone:

sudo rm -f /lib/systemd/system/dump1090-mutability.service /etc/systemd/system/dump1090-mutability.service
sudo reboot

Anyway the snippet you showed just shows that it was running 2 days ago, not that it's running.
So it doesn't really matter.

[HF_ATL]

sudo apt remove dump1090-mutability

This is enough to make sure it no longer runs and interferes with dump1090-fa.

Done that but the result is the same: dump1090-mutability running and dump1090-mutability2 not found.
However dump1090-mutability should have been removed as now "sudo apt remove dump1090-mutability" gives me "Package 'dump1090-mutability' is not installed, so not removed"

[wiedehopf]

sudo apt remove dump1090-mutability

This is enough to make sure it no longer runs and interferes with dump1090-fa.

[HF_ATL]

HF_ATL

sudo update-rc.d -f dump1090-mutability remove 
sudo update-rc.d -f dump1090-mutability2 remove 
sudo systemctl daemon-reload 

sudo rm /etc/init.d/dump1090-mutability
sudo rm /etc/init.d/dump1090-mutability2

sudo reboot

After reboot, check status again

sudo systemctl status dump1090-mutability
sudo systemctl status dump1090-mutability2

I have just done that and rebooted the RPi.
However I got the same output as before: dump1090-mutability running and dump1090-mutability2 not found.

[abcd567]

HF_ATL

sudo update-rc.d -f dump1090-mutability remove 
sudo update-rc.d -f dump1090-mutability2 remove 
sudo systemctl daemon-reload 

sudo rm /etc/init.d/dump1090-mutability
sudo rm /etc/init.d/dump1090-mutability2

sudo reboot

After reboot, check status again

sudo systemctl status dump1090-mutability
sudo systemctl status dump1090-mutability2

[abcd567]

Deleting /etc/lighttpd folder is not asking for trouble if one uninstalls both dump1090-mutability AND lighttpd, and that is what I always do and recommend.

After uninstalling both dump1090-mutability and lighttpd and deleting folder /etc/lighttpd, installing dump1090-fa automatically installs lighttpd again as its dependency, and
generates folder /etc/lighttpd with configuration files for dump1090-fa, without any trace of previous configuration of dump1090-mutability.

[HF_ATL]

HF_ATL:

Since you have initially run script for dump1090-mutability, then uninstalled dump1090-mutability, you think it is completely removed. Just give these two commands to confirm both instances of dump1090-mutability are removed. If both removed, you shall get responce "service not found" for both, else "service not found" for one and "failed" for other.

sudo systemctl status dump1090-mutability

sudo systemctl status dump1090-mutability2

Seems that one instance is running:

sudo systemctl status dump1090-mutability

dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
Loaded: loaded (/etc/init.d/dump1090-mutability; generated)
Active: active (exited) since Wed 2019-10-23 14:10:49 WEST; 1 day 18h ago
Docs: man:systemd-sysv-generator(8)
Process: 411 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, sta

sudo systemctl status dump1090-mutability2

Unit dump1090-mutability2.service could not be found.

[wiedehopf]

While you might not understand why people want to keep their current install, their is no need to ask them to delete the whole /etc/lighttpd folder.
As stated previously it's asking for trouble.

And apart from dump1090-mutability starting because it's still installed, the only other problem i know of is that single file that needs to be removed when switching.
All other files are irrelevant and don't stop dump1090-fa from working.

[abcd567]

Instead of getting into all this complication of what to remove and what not, and still having some garbage left over, it is much cleaner and easier to re-image microSD card and start with a clean setup.

I dont understand why people do not like to re-image when it is very easy and gives the cleanest install.

[wiedehopf]

Removing /etc/lighttpd is just a bad idea.
Removing the dump1090 file from there is perfectly sufficient.

All removing that directory is gonna do is cause trouble.
If you want a fresh system use a fresh system, but i really don't understand removing that folder.

In relation to dump1090, there is exactly one file that needs to be removed.
Removing the /usr/share/dum1090-mutability directory is also completely irrelevant.

Removing the dump1090-mutability package is a good idea if it's still installed.
But if the service is disabled and there is no autostart it doesn't matter either.

[abcd567]

HF_ATL:

Since you have initially run script for dump1090-mutability, then uninstalled dump1090-mutability, you think it is completely removed. Just give these two commands to confirm both instances of dump1090-mutability are removed. If both removed, you shall get responce "service not found" for both, else "service not found" for one and "failed" for other.

sudo systemctl status dump1090-mutability

sudo systemctl status dump1090-mutability2