Network Change & Configuration Management

Reply

Process has timed out and was killed by signal 15.

cwolfe
Techie
Posts: 4
328     1

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?

Highlighted

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

mshamilcm
Techie
Posts: 2
328     1

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 
Do you mean 

Recommended for You