Nagios Support Forum

I am recieving the following error. I tried this yesterday and after completly deleting the service and hosts that i thought were the issue, it still would not verify, it always moved on to something else. So I deleted my snapshot in my VM environment and I am starting over today. reciving the same error, i would like some guidence on how to procede.

Thank you

Error: Service has no hosts and/or service_description (config file '/usr/local/nagios/etc/services/localhost.cfg', starting on line 14)

Nagios Core 4.0.7
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 06-03-2014
License: GPL

Website: http://www.nagios.org
Reading configuration data...
Read main config file okay...
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in host type objects (config file '/usr/local/nagios/etc/hosttemplates.cfg', starting at line 14)
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in host type objects (config file '/usr/local/nagios/etc/hosttemplates.cfg', starting at line 135)
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in service type objects (config file '/usr/local/nagios/etc/servicetemplates.cfg', starting at line 14)
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in service type objects (config file '/usr/local/nagios/etc/servicetemplates.cfg', starting at line 117)
Error: Service has no hosts and/or service_description (config file '/usr/local/nagios/etc/services/localhost.cfg', starting on line 14)
Error processing object config files!


***> 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.

Also i did read your post on 2014 upgrade errors, I tried fixing and then writing and verifying, but with no success. So i am hoping for a more precise push in the direction i need to go,
thank you

Can you attach:
Looks like you may have removed the localhost host in the past ( though that would likely mean you are not monitoring your XI server for whatever reason ) and the services config file became a ghost possibly.

i have rolled back my snapshot, would you like the current, which writes and verifies fine or do you want me to run the upgrade again and send you that one?

i have attached a clip showing that i am monitoring the local host

It works fine now? Meaning it monitors localhost and you do not see errors in the Apply Config? If that's he case I would say we don't need to mess with anything further unless/until there *is* a problem.

No, i deleted my snapshot and rolled the VM back. I have tried it three times and each time before ./upgrade i do a write and verify.
It passes just fine, but I get the error noted above during the 2014 upgrade.
I attached the pic to show you that the localhost was in fact being monitored and did have a description and services attatched. It is not an orphaned host/service.

tmcdonald wrote:It works fine now? Meaning it monitors localhost and you do not see errors in the Apply Config? If that's he case I would say we don't need to mess with anything further unless/until there *is* a problem.

There *IS* a big problem, the upgrade fails, i just set you guys 2400+ dollars for my renewal, I would really like for this to work.

benningtonr wrote:i have rolled back my snapshot, would you like the current, which writes and verifies fine or do you want me to run the upgrade again and send you that one?

We need the post-upgrade config file.

My comment about there being a problem was in reference to rolling back the snapshots before we can take a look at the configs. It's hard to troubleshoot a problem if the configs are in a working state, so while it isn't always ideal leaving a server in a non-functioning state we often will need to in order to gather the appropriate logs, configs, etc. I wasn't implying at all that being unable to upgrade is not a problem, though I can see why it would come across that way.

I will run the upgrade now and send the file. then roll back so I can have the monitoring over night

Thank you
for all the help, it really is appreciated.