Linux Discovery issues CSH

[_benow]

Linux Credential has been tested and validated via the "Test Credential"

Added csh to the MID Servers mid.ssh.shells_supported Configuration Parameter

Added "allow_unsupported_shells" = True to the Unix - Classify multiprobe

When I run discovery error messages are

WARNING: Your password has expired.
Password change required but no TTY available.
Exit status: 1

SSHCommand: Attempted to use a script with unsupported shell

Is the issue with ServiceNow config or a Server Side issue?

[tim_broberg]

TL;DR - csh should work out of the box. I would suggest that you undo your modifications, try again, and examine whatever error it was that pushed you down the path of fiddling with the shell controls.

Details:

SSHCommand needs to be able to do things like edit the path and run scripts or define functions which require it to make use of some shell functions.

The supported shells list that you can edit with mid.ssh.shells_supported is a list of bourne compatible shells, defaulting to bash, sh, ksh. (When the list was named, there was no support for csh, so the name fit better.) Those are the shells we test, but you can add shells like dash if you need to.

There is a hard-coded list of csh-compatible shells: csh and tcsh. These require some different logic, but the functionality SSHCommand needs is available.

Then there's allow_unsupported_shells. This allows running a single, simple command on non-Unix devices as an attempt to allow displaying version information and such on embedded devices that don't happen to allow SNMP. It seemed like a good idea at the time, but I'm not aware of any cases where this has proved actually useful.

Hope this helps,

    - Tim.

[_benow]

Thx Tim

Will update as suggested

[ScienceSoft]

Hi,

every credentials have Order - make the order of the credentials lower so it will be used first - may be another credentials with lower order not working and you need your credentials