- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2025 05:11 AM
I have some servers I am attempting to get Discovery working on. The Server admin has confirmed that everything should be set up. When I try to run Discovery, it gives me the following error:
Unsupported shell 'uvrcbash'. Supported shells are [tcsh, csh, ksh, sh, bash, zsh], and Bourne compatible shells in that list are specified by 'mid.ssh.shells_supported' (defaults to [ksh,sh,bash]).
As well as tput: No value for $TERM and no -T specified (This is repeated in 7 lines but on one message)
and SSHTerminalInteractiveCommand: failed to execute: all commands failed to execute from list cli_commands: show vmdevice
Adding that into the MID server Configuration removes that message, but Discovery still fails. (As in Active, couldn't classify)
Am I missing something or is the server admin missing something?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 12:00 PM
Server admin ran additional commands that aren’t typically done.
\#\# sed -i '1d' /home/DiscoveryUser/.bashrc.d/uvrcc_discovery@servername:~$ \# sed -i '1d' /home/DiscoveryUser/.bashrc.d/uvrc
This allowed Discovery to work even after I removed the additional Bash type from the MID Server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 12:00 PM
Server admin ran additional commands that aren’t typically done.
\#\# sed -i '1d' /home/DiscoveryUser/.bashrc.d/uvrcc_discovery@servername:~$ \# sed -i '1d' /home/DiscoveryUser/.bashrc.d/uvrc
This allowed Discovery to work even after I removed the additional Bash type from the MID Server.