Re: [webmin-l] Host blocked by MySQL daemon on TCP monitor checks

[Jamie C. <jca...@we...>]

On 4/Sep/2006 14:41 Joaquim Homrighausen wrote ..
> 
> Something for the FAQ perhaps:
> 
> I wanted to see if two of our MySQL-servers were alive, so I added a quick
> 'n' dirty monitor (TCP, port 3306). Everything was grand until I installed
> a PHP application on the same server as Webmin (290). After that, I started
> getting "host blocked .. " errors in the PHP application logs. It took
> a while to figure it out, but when I did, I deactivated the TCP/3306 monitors
> and configured Webmin on the two MySQL servers instead, to be aware of
> binaries, paths, etc. Then I added a proper MySQL monitor on the "master"
> machine, and the problem never surfaced agin.
> 
> I don't know what data is sent when doing a "port ping", if it's just a
> socket, but MySQL thought Webmin was trying to do "something" anyway, and
> didn't like the number of attempts without success.

Hi Joaquim,
Thanks for the information - I didn't know that MySQL did this kind of host
blocking. To avoid this, I would recommend using the new 'SQL Query'
monitor type, which can login to a database server, make a query and check
the result..
 
 - Jamie