3.0.1 a few issuses

[Frost, Mark {PBG}]

________________________________

	From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Tom
Thogersen
	Sent: Thursday, April 10, 2008 4:45 PM
	To: nagios-users at lists.sourceforge.net
	Subject: [Nagios-users] 3.0.1 a few issuses
	
	

	Hello,

	            Sorry about the test email I was having problems
getting emails out earlier.  I installed and running 3.0.1 now from a
2.11 install. All is well except for two items:

	 

	            For some reason if I try to setup a service group
the verify procedure now tells me - invalid object definition type
"servicegroup" - I am following the documentation and it is basically
the same stuff that I had running on 2.11

	            The status-map option no longer works there I get a
error: could not read object configuration data.

	 

	Thanks for any help

	 

	Tom

 
The servicegroup error you're getting is because the keyword is
"servicegroups" (plural).  The thing to remember there is that a check
could be a member of more than one servicegroup...
 
I don't use the statusmap so I can't comment on that.
 
Mark
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080410/319afa19/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
-------------- next part --------------
_______________________________________________
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