- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Process has timed out and was killed by signal 15.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2019 11:31 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2019 11:12 AM
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 ########################################################################