Hi ,
We are using monyog 5.3 for monitoring our AWS RDS MySQL instance. We had encountered and issue with AWS where in MySQL services went down for 8 minutes.
However monyog did not trigger any alert at time. By looking at logs we could see that monyog had logged error "Can't connect to MySQL server", but it couldn't append its UDO data file.
Also we have noticed that there was no data collected in monyog for next 2 hours. (note: Data collection interval we have set is 5 mins)
Following are exact logs we got
[5.3] [2015-05-13 07:25:32] [Server: MPSX RDS] src/ymysql.cpp(495) ErrCode:2003 ErrMsg:Can't connect to MySQL server on 'mpsx-prod.cm8ulxn1bw7j.us-east-1.rds.amazonaws.com' (4)
[5.3] [2015-05-13 07:25:32] [Server: MPSX RDS] populateudo.cpp(991) ErrCode:2003 ErrMsg:Can't connect to MySQL server on 'mpsx-prod.cm8ulxn1bw7j.us-east-1.rds.amazonaws.com' (4)
[5.3] [2015-05-13 07:25:32] [Server: MPSX RDS] udomgr.cpp(927) ErrCode:-1 ErrMsg:CollectionThread: Unable to collect data for UDO 'DiskInfo'!
[5.3] [2015-05-13 07:30:02] [Server: MPSX RDS] src/ymysql.cpp(495) ErrCode:2003 ErrMsg:Can't connect to MySQL server on 'mpsx-prod.cm8ulxn1bw7j.us-east-1.rds.amazonaws.com' (111)
[5.3] [2015-05-13 07:30:02] [Server: MPSX RDS] populateudo.cpp(991) ErrCode:2003 ErrMsg:Can't connect to MySQL server on 'mpsx-prod.cm8ulxn1bw7j.us-east-1.rds.amazonaws.com' (111)
[5.3] [2015-05-13 07:30:02] [Server: MPSX RDS] src/ymysql.cpp(495) ErrCode:2003 ErrMsg:Can't connect to MySQL server on 'mpsx-prod.cm8ulxn1bw7j.us-east-1.rds.amazonaws.com' (111)
[5.3] [2015-05-13 07:30:02] [Server: MPSX RDS] populateudo.cpp(991) ErrCode:2003 ErrMsg:Can't connect to MySQL server on 'mpsx-prod.cm8ulxn1bw7j.us-east-1.rds.amazonaws.com' (111)
[5.3] [2015-05-13 07:30:02] [Server: MPSX RDS] udomgr.cpp(927) ErrCode:-1 ErrMsg:CollectionThread: Unable to collect data for UDO 'DiskInfo'!
[5.3] [2015-05-13 07:30:02] [Server: MPSX RDS] udomgr.cpp(927) ErrCode:-1 ErrMsg:CollectionThread: Unable to collect data for UDO 'Tables_Size'!
We need to know what could be root cause behind this ? or Something we are missing on configuration part.
Regards,
Ritesh Raut