21 views

Description

Setting the MID configuration parameter mid.ssh.session_timeout, which sets the timeout before MID Server closes an idle SSH session to a target, has no effect. Instead, the timeout is always 300000 milliseconds (5 minutes).

Steps to Reproduce

1. Set MID configuration parameter mid.ssh.session_timeout = 60000
2. Run a simple SSHCommand probe (for example, 'echo hello') to a Linux target.
Expected result: The "w" command (or other tool which shows sessions) on target will show the SSH session disconnects after about 60 seconds.
Actual Result: Disconnects after about 300 seconds.

Workaround

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In and Intended Fix Version fields to determine whether any versions have or are planned to have a permanent fix.

 


Related Problem: PRB1295941

Seen In

There is no data to report.

Intended Fix Version

Madrid

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-09 15:43:50
Published:2018-08-09