suggestions for upgrading Nagios

[Andreas Ericsson]

Fred wrote:
> I believe there are a number of changed configuration variables that
> will be obvious when you try to start a 1.2 config under 2.0b*, I know
> there were a number of syntax errors when I upgraded.
> 

Don't forget the macros in the notification commands, or we'll be 
answering that particular question for the 16033rd time tomorrow.

> -FredC
> 
> --- Greg Vickers <g.vickers at qut.edu.au> wrote:
> 
> 
>>Matt,
>>
>>Matthew Agle wrote:
>>
>>>Hello,
>>>
>>>            I have currently running Nagios version 1.2 and looking to 
>>>upgrade to 2.04b.  Has anyone done this and/or performed a upgrade and 
>>>if so what suggestions/tips would you have?  Is it easier to upgrade or 
>>>simply install to a different location and point the config files 
>>>there?  Thanks in advance for any feedback!
>>
>>RTFM is your friend. I would very carefully read what is new in version 
>>2.0, in the "What's new in this version" section of the online manual.
>>
>>http://www.nagios.org, Support, Online Documentation, v2.x HTML, Table 
>>of Contents, What's new in this version....
>>
>>If I were you, I would pay special attention to the Hostgroup changes.
>>
>>Take a copy of your 1.x config and run the 2.x binary against it, see 
>>what is broken, that will give you a good starting point.
>>
>>HTH,
>>
>>[p.s.] OK, ok, the only change you *have* to make is moving the new 
>>location of the contact_groups directive... but there's so much other 
>>new and better stuff in v2.x, have a look and see what is applicable to 
>>your situation.
>>
>>-- 
>>Greg Vickers
>>Project Manager, IT Security
>>Information Technology Services
>>Queensland University of Technology
>>L12, 126 Margaret St, Brisbane
>>
>>Phone: (07) 3864 9536
>>Email: g.vickers at qut.edu.au
>>IT Security web site: http://www.its.qut.edu.au/itsecurity/
>>
>>CRICOS No. 00213J
>>
>>
>>-------------------------------------------------------
>>SF.Net email is Sponsored by the Better Software Conference & EXPO
>>September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
>>Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
>>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>>_______________________________________________
>>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
>>
> 
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> 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
> 

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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