Are you interested in our Early Access Program (EAP)? This program allows you to preview code, test in your lab and provide feedback prior to General Availability (GA) release of all Infoblox products. If so, please click the link here.

Network Change & Configuration Management

Reply

Process has timed out and was killed by signal 15.

Techie
Posts: 1
2371     0

When attempting to collect configs from a device, or when executing a Cisco command of "SH RUN", I keep getting the error "Process has timed out and was killed by signal 15."

 

I have tried changing my IP SSH time-out settings, but haven't been able to get the diagnostic execute a Cisco command "SH RUN" to run past 35 seconds before getting the "Process has timed out and was killed by signal 15." error message.

 

is there a setting in NETMRI that can be changed to allow for more time to collect the large config files?

Re: Process has timed out and was killed by signal 15.

Member
Posts: 2
2372     0

You can try adding timeout value to the ad hoc script . 

 

 

Script-Filter:
	true

Script-Timeout:600

Script-Variables:
	$Commands_to_be_Executed	text		"Enter commands here, one per line"

########################################################################
Action:
	Execute Command Batch

Action-Description:
	Execute the commands contained in the Commands_to_be_Executed variable.

Action-Commands:
	$Commands_to_be_Executed

########################################################################
Showing results for 
Search instead for 
Did you mean: 

Recommended for You