Migrating from Nagios 2.0b4 to Nagios 3.03

[Deborah Martin]

Hi,

I'm using Suse 10 / Nagios 3.03. 

I have migrated all of my .cfg files across to Nagios 3.03 and all seems to
work well except that, I still have all the host 
checks still pending on nagios 3.03. But on Nagios 2.0b4, all the hosts have
a status of up. (Each version runs on it's own dedicated box.) 

I only define service checks such as an ssh check per host to ensure a host
is up (ping isn't allowed) 

Is this a known behaviour difference between the versions ? Do I need to
make some changes to this new version ? 

Any pointers / ideas would be much appreciated. 

regards,
deborah 






***************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. 

Any unauthorised distribution or copying is strictly prohibited. 
Whilst Kognitio Limited takes steps to prevent the transmission of viruses via e-mail, we can not guarantee that any email or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. 

Kognitio grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused. 

Kognitio Limited, a company registered in England and Wales. Registered number 0212 7833. Registered Office:  3a Waterside Park, Cookham Road, Bracknell, Berks, RG12 1RB. VAT number 864 4378 92.

Kognitio Inc, a company incorporated in Delaware, principal office 180 North Stetson, Suite 3500, Chicago, IL 60601, USA
***************************************************************************

------------------------------------------------------------------------------
_______________________________________________
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