Question

Problem statement

I want to access a server without asking me the password (will be mentioned in the script) and run a command on that server.

My Code

#!/usr/bin/expect
spawn sudo su - <server_name>
expect "[sudo] password for chronicles:"
set Password "xxxxxxx"
send "$Password\r"
#set timeout 300
send "whoami\r"
send "ls -ltr\r"
expect eof

Output

invalid command name "sudo"
    while executing

Restrictions

• I dont have access rights to change env variables or modify
  .bash_profile / .bashrc.
• su server_name command not allowed

Answer 1

David is right that generally this is a bad idea. There are occasionally good reasons for doing it, or doing something similar (e.g. automatically logging into serial consoles for lights-out management), but you haven’t provided any indication as to why it makes sense for you to do it this way.

Caveats aside, the invalid command name is not coming from the spawn line but from the [sudo] in the expect line. Expect is based on tcl, which treats [] square parentheses as special characters indicating command substitution. Additionally, the value passed to expect is a glob pattern not a fixed string, and [] square parentheses are also special characters in globs. So the answer you are looking for is to quote those characters twice:

    expect "\\\[sudo\\\] password for chronicles:"

Also note that after sending the password you should probably include another expect line to wait for the root shell prompt.