forums › forums › Monyog › Using Monyog › Alert Notifications (occasionally) Not Being Sent Via Smtp
- This topic is empty.
-
AuthorPosts
-
-
December 23, 2014 at 1:48 pm #35125
siddhant
MemberHi,
If MONyog fails to send a notification alert it logs this error in the MONyog.log file. An example error which occurs due to incorrect credentials looks something like this:
smtpcallback.cpp(158) ErrCode:1 ErrMsg:Retrying PLAIN authentication after 535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=14257 fp13sm181179
smtpcallback.cpp(158) ErrCode:2 ErrMsg:Can not authenticate to SMTP server: 535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=14257 fp13sm181179
Please see if you get errors like this logged in your MONyog.log file. If this has anything to do with an error with your SMTP server, the error message can be found here.
Also. please check if you understand the concept of alert-able and have it configured to send alert notification immediately. Please follow these steps:
1. Click on the button in front of the server on the left panel in MONyog and select Edit server.
2. On the edit server page click on the Notification settings tab.
3. Check if the Send notifications over mail(SMTP)? is set to Yes. Also check if your mail settings are properly configured.
4. Now in the Send notification when alert-able set the value to 1.(default if 5)The value in this field 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. But setting it to 1 would ensure that the mail alert is fired the first time it encounters the problem. Please refer to the attached screenshot.
If this still doesn’t solve the issue, please share with us the events.data file for the problematic server in the MONyog’s data directory. Upload it to Dropbox and share with us the link for the same by writing us back to [email protected]
-
December 23, 2014 at 6:55 pm #35126
slibby
MemberHello Siddhant,
We are still not showing any relevant entries in MONyog.log around the time frames when these alerts should have been sent. Also, the “alert-able” configuration has been set to 1 instead of the default value of 5 for all servers since prior to our realization that the alerts were not being sent occasionally.
I am sending an email with the Dropbox links to the events.data files for two of our servers which have been configured to alert on our ‘Notification Test’ monitor. The CSO was originally applied to one server, then we switched it to apply to a different server early this morning.
Thank you,
Steven Libby
-
-
AuthorPosts
- You must be logged in to reply to this topic.