Are '@' symbols allowed in hostnames in Nagios, other than for email addresses? I know special characters are invalid for internet hostnames... If core and DNS1 are showing up, but the other hosts with '@' are not, I think that's your problem.
May I ask why you are using special characters for hostname aliases in Nagios? James Moseley From: Alex Dehaini [mailto:alexdeha...@gmail.com] Sent: 21 January 2009 11:38 To: Steve Burton Cc: Nagios Users Mailinglist Subject: Re: [Nagios-users] Hostgroup Issue Yes, I do have a hostgroup.cfg file. The issue is, when I add a new host or service - it doesn't show up in the cgi interface but nagios has seen it. My entries in hostgroup.cfg file are working, however - since nagios do not see these new hosts and services, they can't be displayed under the hostgroup. I wish there was somewhere I could check investigate this. Here is a snippet from my hostgroup.cfg file define hostgroup{ hostgroup_name CANTOMENTS alias SITE-CANTOMENTS members core,s...@procreditadjangote,DNS1, ap...@cantoments,s...@cantoments,swi...@cantoments } define hostgroup{ hostgroup_name GIX alias GIX members core,bhmas...@gix,bhsl...@kokomlemle2gix,rou...@gix } define hostgroup{ hostgroup_name GT alias GT members core2gt,bhmas...@koko2gt,bhsl...@gt2koko } I added new hosts ap...@cantoments,s...@cantoments and swi...@cantoments and their corresponding services. However, the cgi web interface does not show them - that is the issue. Hosts core and DNS1 are old entries and they come up alright under the hostgroup but the others I added recently are not showing. Here is an image of what I am talking about Alex ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Nagios-users mailing list Nagios-users@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
