Bash – When using expect: SSHFS Transport endpoint is not connected

bashexpectsshfs

When I run my SSHFS connection script from bash, everything works perfectly.

However, when I run the same script using the expect utility, I get the following error when I try to access the folder mount location:

Transport endpoint is not connected

Here is my expect script:

#!/usr/bin/expect -f
spawn standard_sshfs_connection_string_or_script
expect "password: "
send "my_password\r"

Q: Any Ideas?

Note:

I've first already called: fusermount -u mount_location
Is there something about spawn creating a new process, perhaps the sshfs process closes prematurely? (Is there any way to ensure the sshfs process stays open?)

Best Answer

I'm not sure the output of sshfs is caught in expect. This may be your problem - the script terminates without sending the password, which would cause the problem you describe.

Another possible scenario is that sshfs is actually sending you the output user@domain password:, and expect may not like it.

However, this really isn't a good way of dealing with the problem. Your password is in plain text within that script!!

Have you considered using public-key authentication? Take a look at this git example if you don't know how it works.

Related Solutions

Sshfs – transport endpoint is not connected

Your SSHd has not been setup.

Do that first and try again.

Shell – Unix AIX passing variable and arguments to expect and spawn

This isn't doing what you want:

set FILEPATH1 $1

Tcl (and expect) don't use the shell-style $1, $2, ... way of accessing the command line arguments. You want to use the global $argv list:

set FILEPATH1 [lindex $argv 0]

Also, your spawn call is incorrect. sh will be looking for a file named "scp $FILEPATH1 $USER@$HOST:/destination/files". You don't need a shell to spawn scp:

spawn scp $FILEPATH1 $USER@$HOST:/destination/files

Now, where are USER and HOST coming from? Are they environment variables? If so:

spawn scp $FILEPATH1 $env(USER)@$env(HOST):/destination/files

And, you're not waiting for the transfer to actually complete before your script exits. Do this:

expect password:
send "$pass\r"
set timeout -1
expect eof

I'm assuming that you're only prompted for the password once. If you have to enter it multiple times, then

expect {
    password: {
        send "$pass\r"
        set timeout -1
        exp_continue
    }
    eof
}

Best Answer

Related Solutions

Sshfs – transport endpoint is not connected

Shell – Unix AIX passing variable and arguments to expect and spawn

Related Question