MySQL replication broken status in nagios

[vadi]

Hi Mark,

First let me tell thanks for replaying to this mail.
Do you have any script by using check_mysql which is used for showing
replication error in nagios
For example:


mysql> show slave status\G

*************************** 1. row ***************************

             Slave_IO_State: Waiting for master to send event

                Master_Host:

                Master_User: repl

                Master_Port: 3306

              Connect_Retry: 60

            Master_Log_File: lindb200603-bin.000003

        Read_Master_Log_Pos: 775021520

             Relay_Log_File: lindb200604-relay-bin.000247

              Relay_Log_Pos: 1542020

      Relay_Master_Log_File: lindb200603-bin.000003

           Slave_IO_Running: Yes

          Slave_SQL_Running: No

            Replicate_Do_DB:

        Replicate_Ignore_DB:

         Replicate_Do_Table:

     Replicate_Ignore_Table:

    Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

                 Last_Errno: 1064

                 Last_Error: Error 'You have an error in your SQL syntax;
check the manual that corresponds to your MySQL server version for the right
syntax to use near ''c' at line 1' on query.Query: 'update active_sessions
set
val='Y2JheV9zZXNzaW9uOiR0aGlzLT5pbiA9ICcwJzsgJHRoaXMtPnB0ID0gYXJyYXkoKTsg',
changed='20061228080327' where sid='4c142f92c875fd820c81bd71fe03f95f' and
name='c'

               Skip_Counter: 0

        Exec_Master_Log_Pos: 532520812

            Relay_Log_Space: 244044800

            Until_Condition: None

             Until_Log_File:

              Until_Log_Pos: 0

         Master_SSL_Allowed: No

         Master_SSL_CA_File:

         Master_SSL_CA_Path:

            Master_SSL_Cert:

          Master_SSL_Cipher:

             Master_SSL_Key:

      Seconds_Behind_Master: NULL

1 row in set (0.00 sec)


If there is any error in this field Last_Error: it should display this error
massage in nagio and also it should send mail on this issue.

I am not able find replication broken info in nagios Due to this I usually
need to check manually in the database

Please kindly help me

Thanks,

vadiraj


On 1/12/07, Petersen, Mark <MPetersen at gs1us.org> wrote:
>
>   Why can you not use check_mysql –S slave stuff from the standard nagios
> plugins?  If this won't work you'll have to write a script/plugin following
> the guildelines available here -
> http://nagiosplug.sourceforge.net/developer-guidelines.html and/or ask
> more specific questions.
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070113/fe9ecbb7/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null