The service MySQL appears to be down, but it is running

[nat]

CLOUDLINUX 7.4 standard
Cpanel v68.0.37
MariaDB 10.0

---

I updated Cpanel and started to get the following Cpanel Monitoring e-mails:

"The service “mysql” appears to be down."

Mysql is running and working fine.

I reset the MySQL Root password and restarted MySQL but continue to get the emails.

 

[cPanelMichael]

Hello,

Can you run the following command and let us know the output?

/scripts/restartsrv_mysql --status

Additionally, do you notice any recent output to the MySQL error log located at /var/lib/mysql/$hostname.err ?

Thank you.

 

[nat]

(XID mm67v8) The “mysql” service is down.

 

[nat]

# /scripts/restartsrv_mysql --status
(XID bre549) The “mysql” service is down.

-----

161011 15:34:13 mysqld_safe mysqld from pid file /var/lib/mysql/HOSTNAME.pid ended
161011 15:34:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161011 15:34:13 [Note] /usr/sbin/mysqld (mysqld 10.0.27-MariaDB) starting as process 95271 ...
161011 15:34:13 [Note] InnoDB: Using mutexes to ref count buffer pool pages
161011 15:34:13 [Note] InnoDB: The InnoDB memory heap is disabled
161011 15:34:13 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
161011 15:34:13 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
161011 15:34:13 [Note] InnoDB: Compressed tables use zlib 1.2.7
161011 15:34:13 [Note] InnoDB: Using Linux native AIO
161011 15:34:13 [Note] InnoDB: Using CPU crc32 instructions
161011 15:34:13 [Note] InnoDB: Initializing buffer pool, size = 128.0M
161011 15:34:13 [Note] InnoDB: Completed initialization of buffer pool
161011 15:34:13 [Note] InnoDB: Highest supported file format is Barracuda.
161011 15:34:13 [Note] InnoDB: 128 rollback segment(s) are active.
161011 15:34:13 [Note] InnoDB: Waiting for purge to start
161011 15:34:13 [Note] InnoDB:  Percona XtraDB (http://www.XXXXXXX.com) 5.6.31-77.0 started; log sequence number 3597171572
161011 15:34:13 [Note] Plugin 'FEEDBACK' is disabled.
161011 15:34:13 [Note] Server socket created on IP: '::'.
161011 15:34:14 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.27-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
161011 15:38:05 [Note] /usr/sbin/mysqld: Normal shutdown

161011 15:38:05 [Note] Event Scheduler: Purging the queue. 0 events
161011 15:38:05 [Note] InnoDB: FTS optimize thread exiting.
161011 15:38:05 [Note] InnoDB: Starting shutdown...
161011 15:38:07 [Note] InnoDB: Shutdown completed; log sequence number 3597366806
161011 15:38:07 [Note] /usr/sbin/mysqld: Shutdown complete

161011 15:38:07 mysqld_safe mysqld from pid file /var/lib/mysql/HOSTNAME ended

 

[nat]

Solved.

I stopped the mysql pid's and restarted using WebHost Manager.

RECOVERED : mysql (000.000.000.000)


I was restarting it wrong.

# service mysql restart

... starts it differently where it works but Cpanel Monitoring sees it as down.


# service mysqld restart
and
# systemctl restart mysqld
and
WebHost Manager starts it correctly.

 

[cPanelMichael]

Hello,

You may also want to consider restarting it using the following command:

/scripts/restartsrv_mysql

Also, consider reporting this to CloudLinux directly, as it appears to be isolated to MySQL Governor with Percona.

Thank you.