Nagios Support Forum

Posted: **Wed Jan 27, 2016 3:06 am**

Everyone, hello.

I didn't know where I may contribute and contributed to this.
When you can also tell a right contribution place, it's lucky.

I'm quite in trouble.

The PING service is made active in NagiosQL, and would like to eliminate HOSTS, but it's NO.
Error: Could not expand services specified in service escalation
You can't be shown and do non-actively, and I'm in trouble.

How can PING service be done non-actively, and would be able to eliminate HOSTS now?

Nagios Ver. 3.0.6
NagiosQL Ver. 3.0.2

Please help me.

Posted: **Wed Jan 27, 2016 10:31 am**

I have to start with a disclaimer, NagiosQL is not our product, and we do not provide support for it. We can do our best to help you out, but if it comes down to a bug with NagiosQL, there's not a lot we can do about it.

P3_25 wrote:The PING service is made active in NagiosQL, and would like to eliminate HOSTS, but it's NO.

I'm not fully understanding what you're saying here. You don't want to have a ping command for your hosts?

P3_25 wrote:How can PING service be done non-actively, and would be able to eliminate HOSTS now?

You want to have a passive ping service set up? I'm not sure what you mean by eliminating HOSTS.

Posted: **Wed Jan 27, 2016 7:39 pm**

hello.

I am sorry in poor English.

I'm not fully understanding what you're saying here. You don't want to have a ping command for your hosts?

⇒I want to only stop Ping service.

You want to have a passive ping service set up? I'm not sure what you mean by eliminating HOSTS.User avatar

⇒I want to delete the deletion of the host and the Ping service monitoring associated with the host from a monitoring screen of Nagios.

Change all setting; Check configuration file: The following errors were displayed when I let you carry it out
Error: Could not expand services specified in service escala(config file '/usr/local/nagios/etc/serviceescalations.cfg',starting on line234)

Posted: **Thu Jan 28, 2016 3:14 pm**

P3_25 wrote:⇒I want to only stop Ping service.

Can you maybe attach a screenshot with what you want gone?

P3_25 wrote: ⇒I want to delete the deletion of the host and the Ping service monitoring associated with the host from a monitoring screen of Nagios.

You want to configure Nagios from the interface? You may want to look at Nagios XI. Nagios XI is our commercial solution, which aims to take the complication out of Nagios configuration. I would recommend giving the free trial a shot.

P3_25 wrote:Change all setting; Check configuration file: The following errors were displayed when I let you carry it out
Error: Could not expand services specified in service escala(config file '/usr/local/nagios/etc/serviceescalations.cfg',starting on line234)

Did you delete a service but not delete the escalation for it?

Posted: **Fri Jan 29, 2016 12:55 am**

hello.

Did you delete a service but not delete the escalation for it?
　⇒Yes

Posted: **Fri Jan 29, 2016 11:43 am**

Can you post your serviceescalations.cfg for us to review?

Posted: **Sun Jan 31, 2016 11:15 pm**

hello.

It will send the serviceescalations.cfg.
Thank you check .

Code: Select all

###############################################################################
#
# Service escalations configuration file
#
# Created by: Nagios QL Version 3.0.2
# Date:	      2016-01-28 11:07:46
# Version:    Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND --- 
# Nagios QL will overwite all manual settings during the next update
#
###############################################################################

define serviceescalation {
	host_name                     		Brick.IVC,exvn-2k8dc01.ex.isb.co.jp,GW.Chiba,GW.Honsha,GW.Kofu,GW.Mishima,GW.Osaka,GW.Shinyokohama,GW.SMC,L2SW.IVC,L3Sw.Shinyokohama,mail.vn.isb.co.jp,sw.Chiba-4F,sw.Kofu,sw.Mishima,sw.Osaka,sw.Shinyokohama4F,sw.Shinyokohama6F,sw.Shinyokohama7F
	service_description           		*
	contacts                      		ML-Network,ShinjukuDC1
	contact_groups                		ML-Network,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-141
	service_description           		*
	contacts                      		Onogawa_L,ShinjukuDC1
	contact_groups                		Onogawa_L,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-141
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		OBIC-AP01,OBIC-DB01
	service_description           		*
	contacts                      		Sato_K,ShinjukuDC1
	contact_groups                		Sato_K,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		OBIC-AP01,OBIC-DB01
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-123
	service_description           		*
	contacts                      		ShinjukuDC1,Takahashi_S
	contact_groups                		ShinjukuDC1,Takahashi_S
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-123
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		000-sv01
	service_description           		*
	contacts                      		ShinjukuDC1,Umetani_S
	contact_groups                		ShinjukuDC1,Umetani_S
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		000-sv01
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-123-AK2
	service_description           		*
	contacts                      		Eguchi_K,ShinjukuDC1
	contact_groups                		Eguchi_K,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-519
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-519
	service_description           		*
	contacts                      		Miyazaki_M,ShinjukuDC1
	contact_groups                		Miyazaki_M,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		5448-1,5448-11,5448-12,5448-2,8024F-1,8024F-11,8024F-12,8024F-2,BCHmanager,BCSmanager,Brick.Shinjuku,BS01-esxi01,BS01-esxi02,BS01-esxi06,EQ-manager01,EQ-manager11,GW.Shinjuku1,GW.Shinjuku2,GW.Toyosu1,GW.Toyosu2,ISB-ALOG31,ISB-BK01,ISB-BK02,ISB-BK11,ISB-FS10,ISB-VCA01,ISB-VEPO01,ISB-VESXI01,ISB-VESXI02,ISB-VESXI03,ISB-VESXI04,ISB-VESXI503-3,mailhost0-0,MD3001-0C,MD3001-1C,Mdmanager,Nagios1,ns,powerconnect246,powerconnect247,powerconnect252,powerconnect253,Proxy,R815-ESXI12,R815-ESXI13,R815-ESXI14,R815-ESXI15,R815-ESXI16,R815-ESXI17,R815-ESXI18,ws0,ws1
	service_description           		*
	contacts                      		IT,ShinjukuDC1
	contact_groups                		IT,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		5448-1,5448-11,5448-12,5448-2,8024F-1,8024F-11,8024F-12,8024F-2,Brick.Shinjuku,BS01-esxi01,BS01-esxi02,BS01-esxi06,GW.Shinjuku1,GW.Shinjuku2,GW.Toyosu1,GW.Toyosu2,ISB-ALOG31,ISB-BK01,ISB-BK02,ISB-BK11,ISB-FS10,ISB-VCA01,ISB-VEPO01,ISB-VESXI01,ISB-VESXI02,ISB-VESXI03,ISB-VESXI04,ISB-VESXI503-3,mailhost0-0,MD3001-0C,MD3001-1C,Mdmanager,Nagios1,ns,powerconnect246,powerconnect247,powerconnect252,powerconnect253,Proxy,ws0,ws1,www
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		Brick.IVC,exvn-2k8dc01.ex.isb.co.jp,GW.Chiba,GW.Honsha,GW.Kofu,GW.Mishima,GW.Osaka,GW.Shinyokohama,GW.SMC,L2SW.IVC,L3Sw.Shinyokohama,mail.vn.isb.co.jp,sw.Chiba-4F,sw.Kofu,sw.Mishima,sw.Osaka,sw.Shinyokohama4F,sw.Shinyokohama6F,sw.Shinyokohama7F
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		ISB-ISAP01,ISB-ISDB01,ISB-ISUT03,ISB-TREADER
	service_description           		*
	contacts                      		ShinjukuDC1,unno_B
	contact_groups                		InformationSystem,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		ISB-ISAP01,ISB-ISDB01,ISB-ISUT03,ISB-TREADER
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-123-AK2
	service_description           		*
	contacts                      		Eguchi_K,ShinjukuDC1
	contact_groups                		Eguchi_K,ShinjukuDC1
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		jinjiobicsv,TeleTime.Chiba-4F,TeleTime.Chiba-5F,TeleTime.Honsya-8FS,TeleTime.Kofu,TeleTime.Mishima,TeleTime.Osaka,TeleTime.Shinjuku,TeleTime.Shinyokohama-4F_South,TeleTime.Shinyokohama-4F_West,TeleTime.Shinyokohama-5F_West,TeleTime.Shinyokohama-6F,TeleTime.Shinyokohama-7F
	service_description           		*
	contacts                      		iwaki_K,ShinjukuDC1
	contact_groups                		Jinji,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		jinjiobicsv,TeleTime.Chiba-4F,TeleTime.Chiba-5F,TeleTime.Honsya-8FS,TeleTime.Kofu,TeleTime.Mishima,TeleTime.Osaka,TeleTime.Shinjuku,TeleTime.Shinyokohama-4F_South,TeleTime.Shinyokohama-4F_West,TeleTime.Shinyokohama-5F_West,TeleTime.Shinyokohama-6F,TeleTime.Shinyokohama-7F
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-136-cblw
	service_description           		*
	contacts                      		Matusno_M,ShinjukuDC1
	contact_groups                		Matusno_M,ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		EXJP-136-cblw
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		*
	service_description           		*
	contacts                      		ShinjukuDC1
	contact_groups                		ShinjukuDC1
	first_notification            		1
	last_notification             		1
	notification_interval         		30
	}	

define serviceescalation {
	host_name                     		*
	service_description           		*
	contacts                      		ShinjukuDC2
	contact_groups                		ShinjukuDC2
	first_notification            		2
	last_notification             		2
	notification_interval         		30
	}	

###############################################################################
#
# Service escalations configuration file
#
# END OF FILE
#
###############################################################################

Posted: **Mon Feb 01, 2016 6:14 pm**

To test, can you try disabling these two service notifications? I think that the wild cards may be overlapping and causing issues with your other service escalations.

Code: Select all

define serviceescalation {
   host_name                           *
   service_description                 *
   contacts                            ShinjukuDC1
   contact_groups                      ShinjukuDC1
   first_notification                  1
   last_notification                   1
   notification_interval               30
   }   

define serviceescalation {
   host_name                           *
   service_description                 *
   contacts                            ShinjukuDC2
   contact_groups                      ShinjukuDC2
   first_notification                  2
   last_notification                   2
   notification_interval               30
   }

Posted: **Wed Feb 03, 2016 8:58 pm**

hello.

In favor externals were able to carry out successfully setting .

Thank you.

However , another problem has occurred this time .
Are you sure you want to ask ?

Posted: **Thu Feb 04, 2016 10:26 am**

If it's unrelated to this, can you create a new thread for your next question? We try to keep issues to one per thread so avoid confusion.

Are we good to mark the current issue as resolved?

Nagios Support Forum

Error: Could not expand services specified in service escala

Error: Could not expand services specified in service escala

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es

Re: Error: Could not expand services specified in service es