MySQL does not appear to be installed and running on your system

After reading some posts and articles on here I decided to disable "status monitoring" as follows:

  1. Virtualmin | System Settings | Features and Plugins
  2. Deselect "Status monitoring".
  3. Click "Save".

This resulted in the following unsettling error:

Failed to save enabled features : MySQL does not appear to be installed and running on your system, or has not yet been set up properly in Webmin's MySQL Database module. If your system does not use MySQL, it should be disabled in Virtualmin's module configuration page.

MySQL certainly is installed and running on my server!

I returned to Virtualmin | System Settings | Features and Plugins and "Status monitoring" was deselected.

Later I returned again to Virtualmin | System Settings | Features and Plugins and saw that "Status monitoring" was again selected, so I followed the same procedure as above. This time I got the following error:

Failed to save enabled features : The feature Status monitoring cannot be disabled, as it is used by the following virtual servers : [LIST OF DOMAINS REDACTED]

Does this mean I have to go through dozens of domains one by one to disable status monitoring before I can disable it? Or is there a way to disable it on all existing domains?





Howdy -- well, it looks like you're seeing two different issues there.

One, is that for some reason Virtualmin isn't seeing where MySQL is running.

Two, is that the feature does need to be disabled from the individual domains (but we can do that in mass), before it can be removed from the Features and Plugins list.

It sounds like you're saying you aren't currently seeing that first issue, so let's dive into the second one.

You can mass change features by running the command "virtualmin disable-feature". That will show you the available options, then you can use that to disable your desired feature (which would be the "--status" option in your case).

You can also do that from within the GUI. If you go into List Virtual Servers on the bottom-left, you can select all your domains then choose "Update Selected". From there, you can go into "Enabled feature changes" to disable a feature for all those domains.

Once that's done, you should then be able to disable the Status feature in Virtualmin.

Hi Eric,

Thanks for your reply. Sorry for the delay in mine.

I actually disabled the reports for a couple of domains manually through the GUI about a week ago, but I found out yesterday that at least one client was still receiving the reports! Not happy about that.

I've just run the command from the command line, and I'm hoping that will kill them.

Oh, and the MySQL issue was temporarily caused by a transferred in domain that I quickly transferred to its own VPS when it became clear that it needed its own server, so it wasn't technically related to this issue.



Yeah, if a feature is disabled, I wouldn't want my users receiving notifications about it either!

You definitely shouldn't be getting status notifications if that feature is disabled for the domain -- is it also globally disabled as well though? That is, if you go into System Settings -> Features and Plugins, is it disabled there?

Hi Eric,

Well, the status monitoring is now disabled server-wide after I disabled it on all of the domains, but it wasn't before because I hadn't yet disabled it on all domains.

On the domains where I had disabled it manually I noticed the following output when I ran the command:

virtualmin disable-feature --status --all-domains
Updating server ..
    Updating Webmin user ..
    .. done

.. done

Whereas on the domains where I hadn't manually disabled it the output was:

Updating server ..
    Updating Webmin user ..
    .. done

    Removing status monitor for website ..
    .. done

    Removing status monitor for SSL website ..
    .. done

    Removing status monitor for SSL certificate ..
    .. done

.. done


Even though I ran "virtualmin disable-feature --status --all-domains" and deactivated "Status Monitoring" under "Features and Plug-ins" on the server last week, a client has just forwarded me an email sent yesterday that shows that even though I completely disabled the status monitor, it's still sending out emails!

How is this possible?


Could you paste in the contents of the email that they forwarded you, including any email headers

Hi Eric,

Not sure what bearing the headers have, but a heavily redacted version (since this is public) is below of a mail that I too am still receiving, although in an account I don't check every day. I do not have the full headers of the email the client received.

What is even more bizarre about this particular email that I received is that it is for a domain that I also completely removed/deleted from the server last week.

Have to run. Will see your response in a few hours.


Return-Path: <>
Received: from (HELO (
by with (DHE-RSA-AES256-SHA encrypted) SMTP; 19 Apr 2016
04:50:27 +0000
Received: by (Postfix, from userid 0) id 1822C68DC; Tue, 19
Apr 2016 04:50:26 +0000 (UTC)
Subject: Service monitor : Website back up on
Date: Tue, 19 Apr 2016 04:50:26 +0000 (UTC)
Message-Id: <>
Mime-Version: 1.0

Monitor on for 'Website' has detected that the service has gone back up at 19/Apr/2016 04:50

I'm quite puzzled as to why you're still seeing those.

I wanted to see the details of what Webmin was telling you, as well as the time it was saying that (just to rule out a strange mail issue, in case they had been in the queue for awhile).

We may end up needing to get Jamie involved, but one other thing first -- if you go into Webmin -> Others -> System and Server Status, does it show anything there as being monitored?

Hi Eric,

Thanks for your reply. Yes, in addition to various services (Apache, MySQL, etc.), there were (because I have now deleted them) six domain items still being monitored, three for the domain I completely removed from the system last week, and three for the one client that is already annoyed at us.

Should that end all of the monitoring emails?


So, something unusual has been going on, as disabling the status feature should absolutely remove those. It shouldn't be necessary to handle that manually as you just did.

Performing the steps you just did should prevent any further emails, as there's no other functionality remaining that would be performing those checks.

However, since this is all a bit unusual, I'd certainly like to keep an eye on it -- if you see any more, I think we'll need to get Jamie involved and have him take a look.

Hi Eric,

OK, thanks. I don't see any more emails this morning, so that's good.