hi I recently update Nagios Core 3 and now I'm on version 4.0.4 but I lost all my hosts ?
how do I reenter them into the new version ?
I'm new at this and using nconf
please help !
EXPORT OLD NAGIOS
Re: EXPORT OLD NAGIOS
I can't really speak for Nconf since it's not our product, but the configs should still be there depending on how you updated. Can you provide more details as to the process you followed?
Former Nagios employee
-
phil.lay151
- Posts: 3
- Joined: Wed Mar 09, 2016 3:56 pm
Re: EXPORT OLD NAGIOS
Im not sure but if I'm not mistaken I didn't do a upgrade I installed it instead of upgrading :S mistake
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: EXPORT OLD NAGIOS
I've not used nconf but from looking at the documentation:
http://www.nconf.org/dokuwiki/doku.php? ... tart_guide
You need to update nagios.cfg to point to the location that nconf dumps config files.
Further questions should be posted in their forums:
http://forum.nconf.org/
http://www.nconf.org/dokuwiki/doku.php? ... tart_guide
You need to update nagios.cfg to point to the location that nconf dumps config files.
Further questions should be posted in their forums:
http://forum.nconf.org/
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: EXPORT OLD NAGIOS
there is no reason why nconf cannot continue to work, the issue is most likely like box293 has said your configuration before was not in a standard location
I (unlike everyone else apparently) use nconf I love it
I opted on my installation to use a really standard configuration structure for nagios /usr/local/nagios/etc/... if you are not using that structure for your config you might want to consider moving your config there for consistency.
I (unlike everyone else apparently) use nconf I love it
I opted on my installation to use a really standard configuration structure for nagios /usr/local/nagios/etc/... if you are not using that structure for your config you might want to consider moving your config there for consistency.
Looking forward to seeing you all at #NagiosCon2019?
-Dedicated Lover of Nconf,PNP4Nagios and Nagvis
-Dedicated Lover of Nconf,PNP4Nagios and Nagvis
-
phil.lay151
- Posts: 3
- Joined: Wed Mar 09, 2016 3:56 pm
Re: EXPORT OLD NAGIOS
ok I had to change de Nagios.cfg but now I'm getting this error
Whoops!
Error: Could not read host and service status information!
The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running. If Nagios is indeed not running, this is a normal error message. It simply indicates that the CGIs could not obtain the current status of hosts and services that are being monitored. If you've just installed things, make sure you read the documentation on starting Nagios.
Some other things you should check in order to resolve this error include:
1.Check the Nagios log file for messages relating to startup or status data errors.
2.Always verify configuration options using the -v command-line option before starting or restarting Nagios!
Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.
this was in the log file
February 22, 2016 08:00
Program End[02-22-2016 08:18:25] Bailing out due to errors encountered while attempting to daemonize... (PID=27121)
Informational Message[02-22-2016 08:18:25] Failed to obtain lock on file /var/run/nagios.pid: Permission denied
Informational Message[02-22-2016 08:18:25] LOG VERSION: 2.0
Informational Message[02-22-2016 08:18:25] Local time is Mon Feb 22 08:18:25 EST 2016
Program Start[02-22-2016 08:18:25] Nagios 3.2.3 starting... (PID=27121)
can someone please help me... ??????????
Whoops!
Error: Could not read host and service status information!
The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running. If Nagios is indeed not running, this is a normal error message. It simply indicates that the CGIs could not obtain the current status of hosts and services that are being monitored. If you've just installed things, make sure you read the documentation on starting Nagios.
Some other things you should check in order to resolve this error include:
1.Check the Nagios log file for messages relating to startup or status data errors.
2.Always verify configuration options using the -v command-line option before starting or restarting Nagios!
Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.
this was in the log file
February 22, 2016 08:00
Program End[02-22-2016 08:18:25] Bailing out due to errors encountered while attempting to daemonize... (PID=27121)
Informational Message[02-22-2016 08:18:25] Failed to obtain lock on file /var/run/nagios.pid: Permission denied
Informational Message[02-22-2016 08:18:25] LOG VERSION: 2.0
Informational Message[02-22-2016 08:18:25] Local time is Mon Feb 22 08:18:25 EST 2016
Program Start[02-22-2016 08:18:25] Nagios 3.2.3 starting... (PID=27121)
can someone please help me... ??????????
Re: EXPORT OLD NAGIOS
What OS are you using to install Nagios and nconf?
Can you login to your system as root, run the following and post back the output?
Can you post your nagios.cfg file so we can view it?
Can you login to your system as root, run the following and post back the output?
Code: Select all
ps -ef
ll /varBe sure to check out our Knowledgebase for helpful articles and solutions!
Re: EXPORT OLD NAGIOS
were you using mklivestatus before your upgrade?
Looking forward to seeing you all at #NagiosCon2019?
-Dedicated Lover of Nconf,PNP4Nagios and Nagvis
-Dedicated Lover of Nconf,PNP4Nagios and Nagvis
Re: EXPORT OLD NAGIOS
Let us know when you get a chance to answer the above questions @phil.lay151.
Former Nagios Employee