Page 1 of 1

Alerts: "Email to ________" not filling in.

Posted: Wed Mar 16, 2016 9:16 am
by polarbear1
Howdy,

I had this problem on 2015R2, I updated to 1.4.0 and still having the same problem. In my cluster on the Alerting screen where you can see all your alerts, in some cases for my Alert Method, it will say "Email to ________" (blank). If I go to edit the alert, a user is selected, and the emails do get sent out, just the Alerting screen shows a blank and it is really confusing. It only seems to happen with a few specific users. If I edit the alert and choose a different user, it will populate, then I'll go back to change it to the first user, and it will show a blank again. I have a mix of Local and AD users. The users that show a blank are local, but I also have some local users (ex: the local admin account) that does populate correctly, so not totally sure if the AD vs local has anything to do with it.

Thanks.

Re: Alerts: "Email to ________" not filling in.

Posted: Wed Mar 16, 2016 9:41 am
by hsmith
Are any of the AD users showing blank? How many users do you have? I'll try to replicate this. Are you using SSL?

Re: Alerts: "Email to ________" not filling in.

Posted: Wed Mar 16, 2016 9:59 am
by polarbear1
I have 11 AD and 5 Local users. No SSL.

I went through assigning all users to a particular alert, and I noticed that the top of the list (earliest in order of account creation - local and AD) worked as expected. The bottom half of the list (again, both local and AD) came up blank. All the accounts were created over a period of time - maybe couple months worth. I cannot recall what events happened (in terms of NLS updates or otherwise) between the last account that does show, and the first one that is blank.

Re: Alerts: "Email to ________" not filling in.

Posted: Wed Mar 16, 2016 12:52 pm
by hsmith
Confirmed, I'll file a bug report.

Re: Alerts: "Email to ________" not filling in.

Posted: Wed Mar 16, 2016 12:58 pm
by hsmith
Bug report ID is TASK ID 8037. You will be unable to see this as it is an internal system, but you can ask a Nagios team member about it.