Re: [icinga-users] Questions regarding IDO DB and multi master setup

Hi Valentin, On 05/17/2017 10:19 AM, Valentin Höbel wrote: > Hi Lee, > > thanks for taking the time for a) testing this stuff and b) writing an > answer. I appreciate the efforts! > You're welcome! Sorry I don't have a simple answer for you, and I'm certainly not telling you how to set things

Re: [icinga-users] Questions regarding IDO DB and multi master setup

Hi Lee, thanks for taking the time for a) testing this stuff and b) writing an answer. I appreciate the efforts! I tested this and also see it does not failover when I cut off network access to my DB cluster's VIP. However, see below regarding buffering. Good to hear that you experienced th

Re: [icinga-users] Mysql replication monitoring

Is this the icinga notification that you get or output of check_mysql from command line? If it is the icinga notification - could you, please, share your icinga setup, as that is exactly what I try to achieve... Thank you! On Wed, 2017-05-17 at 12:33 +, Kasper Løvschall wrote: > Of course -

Re: [icinga-users] Mysql replication monitoring

Of course - by bad :-) Yup - I get "Slave IO: No Slave SQL: No Seconds Behind Master: (null)" and exit code 2 (CRITICAL). /Kasper -Oprindelig meddelelse- Fra: ST [mailto:smn...@gmail.com] Sendt: 17. maj 2017 14:27 Til: Kasper Løvschall Cc: icinga-users@lists.icinga.org Emne: Re: SV:

Re: [icinga-users] Mysql replication monitoring

Don't stop the whole mysql server - only the replication on your slave (type STOP SLAVE; in your mysql terminal as root user). Otherwise you test mysql server monitoring, not mysql replication monitoring (which can stop even while the server itself runs well). Yes, I run icinga on the slave machin

Re: [icinga-users] Mysql replication monitoring

Hello Kasper, On Wed, 2017-05-17 at 09:23 +, Kasper Løvschall wrote: > I can get the check_mysql command to work without issues: > > ./check_mysql --check-slave > Uptime: 1038854 Threads: 1 Questions: 803933 Slow queries: 0 Opens: 48 > Flush tables: 1 Open tables: 42 Queries per seco

Re: [icinga-users] New Services without notifications until that they are Ok

On Wednesday 17 May 2017 at 11:04:50, Christian Moreno Moreno wrote: > Hi, > > Sometimes our hosts are in icinga and the deployments are not finish so are > some checks that are directly Critical. > Would be possible to configure icinga for that new services that are > directly critical doesnt pr

[icinga-users] New Services without notifications until that they are Ok

Hi, Sometimes our hosts are in icinga and the deployments are not finish so are some checks that are directly Critical. Would be possible to configure icinga for that new services that are directly critical doesnt produce one notification? Some Idea? Regards, Christian Christian Moreno Moreno

Re: [icinga-users] Mysql replication monitoring

Hi again, I can get the check_mysql command to work without issues: ./check_mysql --check-slave Uptime: 1038854 Threads: 1 Questions: 803933 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 42 Queries per second avg: 0.773 Slave IO: Yes Slave SQL: Yes Seconds Behind Master: 0|Conn

Re: [icinga-users] Mysql replication monitoring

Thank you very much for your response! I did read about the Percona Monitoring Plugin, but thought that using standard plugins, available as Debian package should be better, especially if I plan to use Ansible in future to configure my Icinga setup... I'll definitely use your suggestion if I don'

Re: [icinga-users] Mysql replication monitoring

Hi ST! I can recommend a different approach using the Percona Monitoring Plugins (available for free at https://www.percona.com/software/database-tools/percona-monitoring-plugins). It has (among others) two check commands: pmp-check-mysql-replication-running and pmp-check-mysql-replication-del