
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2022 06:40 AM
Hi ServiceNow friends,
We recently noticed that we can't run Sudo -l from the command prompt in Linux or any Linux related patterns. I get this error:
Execution of command sudo -l on host xx.xx.xx.xx failed with status 127. bash: -l: command not found
We checked and compared the MID server specific and global properties with other ServiceNow instances and could not figure out why this is happening.
I can't run some sudo commands like these below as well.
nmcli -t
adinfo -v
adinfo -z
This is only happening in the development instance only. In Production and test environment it works fine.
Any feedback is helpful and highly appreciated.
Thank you
bk
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2022 07:45 AM
I did more test and found that the mid.sa.ssh.use_sncssh was the one causing the issue and after setting it to false, the sudo commands working fine.
Thank you
bk

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2022 07:29 AM
Hi all,
After a comprehensive compare between different SN instances on MID Server global properties I found some properties that were different and I updated them to be just like the ones in Prod instance and the sudo commands started working fine now.
The properties that I changed in Dev instance are these and I think the first two might have something to do with it but I didn't test each property at a time (time consuming cause I should restart the MID service each time).
allow_unsupported_shells set to false
mid.sa.ssh.use_sncssh set to false
mid.sm.discolog.max_object_size changed from 10000 to 1000
mid.uprgade.disable_cleanup changed to false
mid.win.baseboard.or.bios.insertion changed to false
Just wanted to let you all know about this.
Thank you
bk

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2022 07:45 AM
I did more test and found that the mid.sa.ssh.use_sncssh was the one causing the issue and after setting it to false, the sudo commands working fine.
Thank you
bk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 10:52 AM
Hi @BK14 .
Thanks for the info so the in final update did you only change the " mid.sa.ssh.use_sncssh " sys prop to set it to "true" did you revert the other changes as you mentioned in the thread.
Also did you check what is the ramifications of the change and did you observe any issues after this change was made.
allow_unsupported_shells set to false
mid.sa.ssh.use_sncssh set to false
mid.sm.discolog.max_object_size changed from 10000 to 1000
mid.uprgade.disable_cleanup changed to false
mid.win.baseboard.or.bios.insertion changed to false