Hi Julien, Julien TOUCHE wrote: > Hello > > i'm trying to migrate my nagios install on 3.0. i use openbsd (4.4) with > nagios port. > > after updating my configuration with (1), i get > > > # nagios -v `pwd`/nagios.cfg > > Nagios 3.0.3 > Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org) > Last Modified: 06-25-2008 > License: GPL > > Reading configuration data... > > > ***> One or more problems was encountered while processing the config > files... > > Check your configuration file(s) to ensure that they contain valid > directives and data defintions. If you are upgrading from a previous > version of Nagios, you should be aware that some variables/definitions > may have been removed or modified in this version. Make sure to read > the HTML documentation regarding the config files, as well as the > 'Whats New' section to find out what has changed. > <<< > > Same thing if i comment all lines with cfg_file= > same with example files from the port, which i suppose are the ones from > nagios distrib. > Please note, i've remove all files from previous install, only > restoring/updating config. > > As there is no file/line highlighted to look for the error, i don't know > what to do. i didn't have any problems on 2.9. > > > any ideas to locate error ? >
Errors from the configuration check are usually printed inline with the output - check the entire output from Nagios and it should give you the relevant line. Andy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
