Page 1 of 2
Upgrade failing!!!
Posted: Thu Jun 12, 2014 1:28 pm
by BanditBBS
Got this while upgrading:
Code: Select all
make[1]: Leaving directory `/tmp/nagiosxi/subcomponents/nagioscore/nagios-4.0.6'
Running configuration check... CONFIG ERROR! Restart aborted. Check your Nagios configuration.
Went and verified config and got this:
Code: Select all
Nagios Core 4.0.6
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 04-29-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 99)
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 120)
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 401)
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 78)
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 106)
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 854)
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.
Umm, help?
EDIT: I went and deleted that free variable and am now writing the config and trying again
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 1:35 pm
by BanditBBS
Upgrade still stopping in same place and I am now getting this:
Code: Select all
Nagios Core 4.0.6
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 04-29-2014
License: GPL
Website: http://www.nagios.org
Reading configuration data...
Read main config file okay...
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.
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 1:50 pm
by sreinhardt
*Most likely* this is an improper escalation definition. Try deactivating your host and service escalations from within CCM then write and verify. If this passes you should be able to continue with the upgrade. Once it is complete, we can work out what is actually missing, more often than not it is missing a host_name as CCM was not defining that as mandatory.
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 1:55 pm
by BanditBBS
sreinhardt wrote:*Most likely* this is an improper escalation definition. Try deactivating your host and service escalations from within CCM then write and verify. If this passes you should be able to continue with the upgrade. Once it is complete, we can work out what is actually missing, more often than not it is missing a host_name as CCM was not defining that as mandatory.
Holy crap, I love you Spenser!
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 2:01 pm
by abrist
Is it resolved good sir?
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 2:34 pm
by BanditBBS
abrist wrote:Is it resolved good sir?
The install completed and I fixed gearman
Escalations are all broken now
It is not liking these:
Code: Select all
define serviceescalation{
host_name *
servicegroup_name dba_oncall
contact_groups dba
first_notification 500
last_notification 0
notification_interval 15
}
define serviceescalation{
host_name *
servicegroup_name client_server_oncall
contact_groups client_server_pri
first_notification 1
last_notification 0
notification_interval 30
}
define serviceescalation{
host_name *
servicegroup_name client_server_oncall
contact_groups client_server_sec
first_notification 2
last_notification 0
notification_interval 30
}
define serviceescalation{
host_name *
servicegroup_name client_server_oncall
contact_groups client_server_all
first_notification 500
last_notification 0
notification_interval 30
}
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 2:41 pm
by abrist
Just out of curiosity, if you set a service_description on those escalations, does the config verify?
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 2:46 pm
by BanditBBS
Check this out...troubleshooting with just one...changed it to this:
Code: Select all
define serviceescalation{
hostgroup_name *
servicegroup_name dba_oncall
service_description *
contact_groups dba
first_notification 500
last_notification 0
notification_interval 15
}
And verify now works. Will that give me the functionality that I desire? basically any host and any service as long as it belongs to the servicegroup?
EDIT: I logged in as a member of the dba_oncall group and he could see all services, so this is not the fix I need. All I have to say, this worked in 2012...any clue how to resolve?
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 3:06 pm
by sreinhardt
He can see all services, as technically he is a contact via escalation for all services now via:
service_description *
Could you negate the *..? with service_description !* not sure if that would actually work or not, and how it would react with your service group, but it's worth a shot.
Otherwise I think we can all agree that this is very likely a bug in core with regards to accepting either service_name and servicegroup_name but we should never force just service_name.
Re: Upgrade failing!!!
Posted: Thu Jun 12, 2014 3:14 pm
by BanditBBS
Wow, Spenser is my hero today. I can't believe it, but that worked!
Singing "Wind beneath my wings" in my head right now, dedicated to you!