MySQL test caused Got an error reading communication packets

Issue #838 closed
Giacomo created an issue


I guess this is related to #54.

On my Debian 9 server I’ve got Monit 5.20.0 and Mysql 5.7.26.
The Mysql check is:

check process mysql with pidfile /var/run/mysqld/
            group database
            start program = "/etc/init.d/mysql start"
            stop program = "/etc/init.d/mysql stop"
            if failed host port 3306  then restart
            if 5 restarts within 5 cycles then timeout #        

In the Mysql logs I see, at every check this:

[Note] Got an error reading communication packets

As mentioned in Issue #54, I tought this was fixed in Monit > 5.8. I didn’t see this logs in Mysql 5.6.

Is this a regression?

Comments (1)

  1. Tildeslash repo owner

    Use if failed port 3306 protocol mysql then xxxx. Note, mysql protocol test is for MySQL 5.x and not updated for MySQL 8.x

  2. Log in to comment