Can I uninstall MySQL on DNS Only servers?

[Kent Brockman]

Hey guys. I'm wondering if it could be healthy to disable MySQL in the DNS Only's Service Manager, cause it is not being used, even by cpHulk at all, and yet it does use a lot of server memory. I lurked thru the /var/lib/mysql folders and didn't found recently modified folders nor data files. So, can you confirm if MySQL/MariaDB is being used at all for any service in a DNS Only server?

Regards

 

[quietFinn]

We have MySQL server disabled in DNS Only servers without problems (but cPHulk is disabled also).

 

[cPRex]

Sure - if you aren't using any tools that require databases it's fine to disable that.

 

[Kent Brockman]

Sure - if you aren't using any tools that require databases it's fine to disable that.

That's why I asked in the first place: does cpHulk require MySQL to do its work? I don't see any other database in /var/lib apart from the mysql internal ones, and one allegedly belonging to cphulk but its datafiles last modified date seems to be unchanged since 2019.

 

[cPRex]

Since version 62, cPHulk uses an SQLite database and not MySQL.

 

[Kent Brockman]

Great. So you could say that under a standard and up to date DNS Only setup, YOU DONT NEED TO HAVE MYSQL INSTALLED. Is this correct?

Just to be very aware of this, when was the v62 released?

 

[cPRex]

Yes, correct.

62 came out in 2016.

 

[cPRex]

You could also just turn the service off as well before removing it to ensure there are no conflicts, but I would not expect any.

 

[Kent Brockman]

You could also just turn the service off as well before removing it to ensure there are no conflicts, but I would not expect any.

I exactly did that now, and let's wait a couple days to be sure no problems arise at all.

 

[Kent Brockman]

Yes, correct.

62 came out in 2016.

That's pretty odd. If this server was originally installed at the end of 2017, so cpHulk was already using sqlite, why would the install script have installed and enabled MySQL if it's no need? Maybe a forgotten routine? Then make dev staff check if current install script is still deploying MySQL or not, and if so, why would it be needed? ;-)

 

[Kent Brockman]

Talking about oddities on DNS Only... I bring one more thing to make your devs hate me (LOL): by looking the list of processes I found wp-toolkit is present on DNS Only. What the...? See:

# ps aux|grep toolkit
wp-tool+  1454  0.0  0.6 362544  3432 ?        Ss   Sep22   0:01 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
wp-tool+  1457  0.0  0.4 372832  2396 ?        Ss   Sep22   1:02 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php

I solved it running rpm -e wp-toolkit-cpanel as its explained at How do I uninstall WordPress Toolkit?
But how is that possible on DNS Only? Check those upgrade processes. It should be automatically deleted on future iterations from DNS Only as it is consuming a bit of precious memory.

Regards

 

[cPRex]

Just to confirm, did this server start life as a DNSOnly box, or was a conversion made from a full cPanel system?

 

[Kent Brockman]

It was fully installed as a DNS Only box from scratch, on a new server on 2017.

 

[cPRex]

Alrighty - let me do some testing on a modern install and I'll let you know what I find out!

 

[cPRex]

Okay, I built a shiny new DNSOnly system on CentOS 7. I do have MySQL 5.7 installed.

I don't have any WordPress Toolkit RPMs present. We do have a series of cases that removed functionality from DNSOnly that wasn't supposed to be there, so you're likely seeing leftovers of an older install that has been updated rather than what a new one looks like if you were to deploy today.

Does that help at all? You can always use the WHM >> Service Manager to disable the services and see how that goes before you perform a full removal of the tool, just in case you do find it ends up being needed.