Why I got this error: Error; job finished with status ERROR: SSH channel 116 timeout in state TERMINAL_REQUESTED. (timeout.channel_ready = 120000)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-25-2015 12:22 PM
We're evaluating the Fuji Patch 10 version of Discovery and I had problems with a probe, The Linux Storage Probe.
It kept returning this error:
Error; job finished with status ERROR: SSH channel 116 timeout in state TERMINAL_REQUESTED. (timeout.channel_ready = 120000)
I'll skip the long story and give you the quick rundown on the reason and the fix.
The reason revolves around the account used by ServiceNow's midserver to login to Linux systems to run probes. This account needs entries in the sudo permission file to run certain commands and our admins utilize the "full path" to the executable for our entries.
When our Linux admins setup the sudo permissions, they followed the guidance provided by ServiceNow in this document:
link: Credentials - ServiceNow Wiki
In this document, certain commands are listed as being in /usr/bin. In our case, some commands actually are found in /sbin, NOT /usr/bin.
So when the Linux Storage probe attempts to run the command, it prompts for a password for a command which will NOT be allowed to run under sudo.
This hangs the script and results in the timeout., _and_ the error mentioned above.
The fix is to have the Linux admin change the sudo entry for any command not actually in the expected location to use the actual location. In our case, use /sbin/multipath instead of /usrt/bin/multipath.
I wanted to post this in the event that someone else runs into this problem. It might save them some time debugging.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2021 12:55 PM
Hi Sean,
Can you please share the link one more time what is the resolution for that error?
above link is not working.
Best,
Chavan