Strange contact group behavior in 2.0b3

[Benjamin Rutter]

I'm running Nagios v2.0b3 and have a strange problem with contact groups

Here is a breakdown of the issues:

- I create 2 contacts, one called 'brutter' and another 'tward'
- I then create a contact group called 'TRMStaff' and add both users
- Any service I set the contact group of 'TRMStaff' to works flawlessly
- Any host I set the contact group of 'TRMStaff' to works flawlessly

So at this point, all is well...then the strange part

- I create a new contact called 'lgroup'
- I then create a contact group called 'LG' and add the 'lgroup' user
- Any service I set the contact group of 'LG' to works fine AS LONG AS the
HOST of that service is set to 'TRMStaff' as the contact group.


If I have a host with contact group 'TRMStaff' and a service of that host
with contact group 'LG', everything works as it should.

As soon as I change the contact group on the host to 'LG', that host
disappears from the list of hosts in the GUI and alerts are not generated
for the hosts OR the services related to that host.

I have tried creating multiple groups with all sorts of different names and
assigning different users to no avail....

I need to be able to have the 'LG' contact group assigned to both HOSTS and
it's corresponding services.

I have checked the syntax up and down a hundred times and everything seems
to be on point. Is there anything illegal in the group or contact names that
I've chosen?

Any suggestions out there??? This is killing me... 
 




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null