At some point I installed the MySQL addon and removed it later when I decided to use postgres. However, MySQL is still left running on my system and enabled as a systemctl service, even after reboot. if I stop it and disable it with systemctl, it comes back on the next reboot. Is MySQL required to be running on Readynas OS6 in order to support some basic services? I didn't install any addons that make use of it I don't think, all I did was install the MySQL addon, and PHPMyAdmin, but i never even went in there and created a DB or anything. I removed both addons, but mysql is still around. What gives? I am finding the same problem with leafp2p, when I stop and disable that systemctl service, after reboot its back running again. These things are getting bootstrapped into systemctl somehow...perhaps by readynasd, I don't know. Can anyone explain this or help me to get rid of MySQL (and leafp2p)?

Dewdman42 wrote: At some point I installed the MySQL addon and removed it later when I decided to use postgres. However, MySQL is still left running on my system and enabled as a systemctl service, even after reboot. if I stop it and disable it with systemctl, it comes back on the next reboot. The "MySql Server" app is just like the "Postgresql 9.1" app. Simply a meta-package to install the version from Debian. Removing the app will only remove files from the app package itself, not the dependent packages. So on app uninstall you still have the Debian package installed. MySQL doesn't install a systemd service, systemd is just translating the init script, so enable/disable won't work. You need to update-rc.d mysql disable. Is MySQL required to be running on Readynas OS6 in order to support some basic services? I didn't install any addons that make use of it I don't think, all I did was install the MySQL addon, and PHPMyAdmin, but i never even went in there and created a DB or anything. I removed both addons, but mysql is still around. MySQL is not required for core NAS functionality. Some apps depend on MySQL, same story as above. If they're depending on the Debian package it won't get removed on app uninstall. I am finding the same problem with leafp2p, when I stop and disable that systemctl service, after reboot its back running again. These things are getting bootstrapped into systemctl somehow...perhaps by readynasd, I don't know. Can anyone explain this or help me to get rid of MySQL (and leafp2p)? You don't have any of the leafp2p dependent services enabled, do you? Replicate, Remote, ReadyCLOUD...

Yes I tried to use systemctl disable on everything mentioned. They came back on boot. No I don't have any cloud services enabled. I may have TRIED to enable ReadyCloud once, but it didn't work and I turned it off in front view. what I can say is that numerous addons leave Sh__T hanging around..that's all i can say. I'm going to do a factory reset and be careful not to install anything I don't want to get stuck with, like mysql, readycloud, rsyslog, etc.

I edited my reply above. systemd will translate init.d service so you can start and stop them, but enable and disable won't work. Need to use update-rc.d. I suspect the leafp2p issue is the same.

so... update-rc.d mysql remove , oughta get rid of mysql it sounds like. Got rid of rsyslog with that too. hopefully between that and the systemctl disable, they are both gone now.

let me ask you a question since you sound knowledgable. Why are some of those services being added both to the init.d service area as well as systemd? I added my own systemd service unit to startup stunnel and I didn't have to add anythign under the rc-d area at all...it just seems to work. Why do those others use both?

how to get rid of Mysql systemctl

12 Replies

Replies have been turned off for this discussion

siigna
NETGEAR Employee Retired
Apr 16, 2016
Dewdman42 wrote:

At some point I installed the MySQL addon and removed it later when I decided to use postgres. However, MySQL is still left running on my system and enabled as a systemctl service, even after reboot. if I stop it and disable it with systemctl, it comes back on the next reboot.

The "MySql Server" app is just like the "Postgresql 9.1" app. Simply a meta-package to install the version from Debian. Removing the app will only remove files from the app package itself, not the dependent packages. So on app uninstall you still have the Debian package installed.

MySQL doesn't install a systemd service, systemd is just translating the init script, so enable/disable won't work. You need to update-rc.d mysql disable.

Is MySQL required to be running on Readynas OS6 in order to support some basic services? I didn't install any addons that make use of it I don't think, all I did was install the MySQL addon, and PHPMyAdmin, but i never even went in there and created a DB or anything. I removed both addons, but mysql is still around.

MySQL is not required for core NAS functionality. Some apps depend on MySQL, same story as above. If they're depending on the Debian package it won't get removed on app uninstall.

I am finding the same problem with leafp2p, when I stop and disable that systemctl service, after reboot its back running again. These things are getting bootstrapped into systemctl somehow...perhaps by readynasd, I don't know. Can anyone explain this or help me to get rid of MySQL (and leafp2p)?

You don't have any of the leafp2p dependent services enabled, do you? Replicate, Remote, ReadyCLOUD...
- Dewdman42
  Virtuoso
  Apr 16, 2016
  Yes I tried to use systemctl disable on everything mentioned. They came back on boot. No I don't have any cloud services enabled. I may have TRIED to enable ReadyCloud once, but it didn't work and I turned it off in front view.
  
  what I can say is that numerous addons leave Sh__T hanging around..that's all i can say. I'm going to do a factory reset and be careful not to install anything I don't want to get stuck with, like mysql, readycloud, rsyslog, etc.
  - siigna
    NETGEAR Employee Retired
    Apr 16, 2016
    I edited my reply above. systemd will translate init.d service so you can start and stop them, but enable and disable won't work. Need to use update-rc.d. I suspect the leafp2p issue is the same.