allow_unsupported_shells

[Community Alums]

Getting allow_unsupported_shells error while running linux discovery ,

Is there is any way drill which shell it is not supporting ?

Also do we need to add property"allow_unsupported_shells" for each and every linux probe ?

thanks in advance

[RGreene]

My one question on setting allow_unsupported_shells is what probe to set it for?  When you get the error allow_unsupported_shells is false it does not tell you which probe was used.

[tim_broberg]

It didn't tell you what the shell was? This is one of those things where I never seem to have a problem seeing it, but I can't remember how.

What's happening is, SSHCommand connects to the server and runs echo $0.

You can go do that manually and see, or you can squint at the ecc_queue input and try to figure it out, or you can enable debug in the probe or mid.ssh.debug in the mid and look at the agent log to see what happens when it runs echo $0. Personally, I would lean towards the manual approach.

You will probably find that this is either a quirky device, not a server at all, or else it's a different variant of bash like rbash.

If it's a bash, you can add it to the list of bourne-compatible shells and it should just work.

If it's a weird non-server thing, you may need to add another subprobe to Unix - Classify to figure out what kind of a thing this is, and set allow unsupported shells in there. Getting it not to fail on the other subprobes may probe challenging, as multiprobes fail if any subprobe fails. (Pet peeve.)

Please keep us posted on your progress, we'd love to hear it,
    - Tim.

[Community Alums]

Hello Tim ,

After setting property to true ,We are getting below error 

Error; job finished with status ERROR: SSH channel 5 activity timeout in state EXECUTING. (timeout = 120000) com.snc.ssh.SSHTimer@cc7bcf while in state EXECUTING

[tim_broberg]

Ok, so SSHCommand is running some command which neither completes nor delivers any data within 2 minutes.

You can try logging into the thing manually to see if this is a healthy, responsive ssh server, or you can enable debug and look at the details in the agent log.
    - Tim.

[tim_broberg]

"Is there is any way drill which shell it is not supporting?"

It should appear in the <output> of the probe (ecc_queue record, queue=input), but you can login to the system in question as the user you run discovery as and run "echo $0" to see the default shell.

"Also do we need to add property allow_unsupported_shells for each and every linux probe?"

Avoid allow_unsupported_shells as much as possible. Without a supported shell, you can't do things like run scripts or set paths, which are very important.

If there is a weird shell that is sufficiently well-behaved, try adding your shell to mid.ssh.shells_supported.