sajesh.singh
2013-04-29 20:19:46 UTC
sajesh.singh [http://community.zenoss.org/people/sajesh.singh] created the discussion
"MySQL monitoring oddity"
To view the discussion, visit: http://community.zenoss.org/message/73006#73006
--------------------------------------------------------------
I am having some strange MySQL monitoring issues. The MySQL client that I monitor with Core 4.2.2 and the MySQL template works most of the the time, but about 4-5 times a day the status fails with the following error:
2013-04-29 14:08:22,446 DEBUG zen.zencommand: Queued event (total of 2) {'eventKey': 'mysql', 'severity': 4, 'device': 'hostname.domainname', 'eventClass': '/App/MySQL', 'component': 'MySQL', 'summary': 'Datasource MySQL/mysql command timed out'}
'Traceback (most recent call last):\n File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.MySqlMonitor-2.2.0-py2.7.egg/ZenPacks/zenoss/MySqlMonitor/libexec/check_mysql_stats.py", line 75, in <module>\n   cmd.run()\n File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.MySqlMonitor-2.2.0-py2.7.egg/ZenPacks/zenoss/MySqlMonitor/libexec/check_mysql_stats.py", line 35, in run\n   db=\'\', user=self.user, passwd=self.passwd)\n File "/opt/zenoss/lib/python/pymysql/__init__.py", line 93, in Connect\n   return Connection(*args, **kwargs)\n File "/opt/zenoss/lib/python/pymysql/connections.py", line 504, in __init__\n   self._connect()\n File "/opt/zenoss/lib/python/pymysql/connections.py", line 663, in _connect\n   sock.connect((self.host, self.port))\n File "/opt/zenoss/lib/python2.7/socket.py", line 224, in meth\n   return getattr(self._sock,name)(*args)\nKeyboardInterrupt\n
It is almost immediately resolved, but this does cause me to get some unwanted notifications. I know that I can filter the notifications, but would prefer not to go down that route, but try to fix the issue. Anyone have any ideas as to what could be causing this?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73006#73006]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"MySQL monitoring oddity"
To view the discussion, visit: http://community.zenoss.org/message/73006#73006
--------------------------------------------------------------
I am having some strange MySQL monitoring issues. The MySQL client that I monitor with Core 4.2.2 and the MySQL template works most of the the time, but about 4-5 times a day the status fails with the following error:
2013-04-29 14:08:22,446 DEBUG zen.zencommand: Queued event (total of 2) {'eventKey': 'mysql', 'severity': 4, 'device': 'hostname.domainname', 'eventClass': '/App/MySQL', 'component': 'MySQL', 'summary': 'Datasource MySQL/mysql command timed out'}
'Traceback (most recent call last):\n File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.MySqlMonitor-2.2.0-py2.7.egg/ZenPacks/zenoss/MySqlMonitor/libexec/check_mysql_stats.py", line 75, in <module>\n   cmd.run()\n File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.MySqlMonitor-2.2.0-py2.7.egg/ZenPacks/zenoss/MySqlMonitor/libexec/check_mysql_stats.py", line 35, in run\n   db=\'\', user=self.user, passwd=self.passwd)\n File "/opt/zenoss/lib/python/pymysql/__init__.py", line 93, in Connect\n   return Connection(*args, **kwargs)\n File "/opt/zenoss/lib/python/pymysql/connections.py", line 504, in __init__\n   self._connect()\n File "/opt/zenoss/lib/python/pymysql/connections.py", line 663, in _connect\n   sock.connect((self.host, self.port))\n File "/opt/zenoss/lib/python2.7/socket.py", line 224, in meth\n   return getattr(self._sock,name)(*args)\nKeyboardInterrupt\n
It is almost immediately resolved, but this does cause me to get some unwanted notifications. I know that I can filter the notifications, but would prefer not to go down that route, but try to fix the issue. Anyone have any ideas as to what could be causing this?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73006#73006]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]