Data Collection Had Stopped With Error Message —- Udomgr.cpp(927) Er

[Ritesh_Raut]

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

 

[siddhant]

Hi,

 

You didn’t receive the alert because the alert-able value in the notification settings must have been set to a greater value than one. This value specifies the number of consecutive times for MONyog to encounter the same problem before sending the mail alert. In simple words, if set to 5 then MONyog needs to encounter the same problem for 5 consecutive times(or 5 consecutive data collections) before sending the mail alert. For example if set to 5 and the data collection interval in 5 minutes then MONyog will have to face the issue for 5*5 = 25 minutes before sending the alert. But setting it to 1 would ensure that the mail alert is fired the first time it encounters the problem. To do this click on edit server > Notification settings > Send notification when alert-able = 1.

 

Regarding the issue that you faced with MONyog unable to collect data for the next two hours, please write back to us at [email protected] with the following details:

 

1). Have you restarted or edited the server so as to resume the data collection or it resumed on it’s own?

 

2). Please send us the MONyog.log file. Depending on the OS and the mode of installation it can be found in one of the following location:

 

Linux

tar: /MONyog/MONyog.log

rpm: /usr/local/MONyog/MONyog.log

 

Windows

exe: ProgramDataWebyogMONyogMONyog.log

 

3). Also, send us the mysql.data file for the server in question. To know the directory associated with that particular server, hover the mouse pointer over the server name in the left panel of MONyog and note the displayed directory number(something like 0001). Now head over to the MONyog folder described above and navigate to /data//mysql.data

[Author]

Posts