nohup导致“读取密码：无法打开/dev/tty”

Question

我有一个简单的远程ssh脚本命令nohupssh。嘘

sleep 30
ssh -v  -l developer server11  "/usr/local/jdk1.7.0_45/bin/jmap -histo:live 1770;"

我按如下方式运行脚本：

nohup nohupssh.sh > out.log 2>&1 & 

当我如上所示执行它时，jmap实用程序在远程服务器上成功执行。但是，如果按照上面所示执行它并退出bashshell，则会出现如下所示的错误。

请注意，我在本地和远程服务器上都有一个正确格式化的authorized_keys。另外请注意，由于这两个服务器是共享的，所以这两个服务器都没有id_rsa。

我试过很多组合：

ssh -v -A -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o GlobalKnownHostsFile=/dev/null server11 .... 

但是没有用。我仔细检查了ssh的手册页，寻找线索，尝试了各种选择。我认为必须有一个或一组ssh选项来解决这个问题。真正的脚本（而不是上面的节略）也有scp。因此，我希望我所回避的选项对scp和ssh都有效。

完整的详细日志是

OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /home/developer/.ssh/config
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to server11 [10.255.10.20] port 22.
debug1: fd 4 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file /home/developer/.ssh/identity type -1
debug1: identity file /home/developer/.ssh/id_rsa type -1
debug1: identity file /home/developer/.ssh/id_dsa type -1
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
Warning: Permanently added 'server11,10.255.10.20' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
****************************************************************************
WARNING: Unauthorized access to this system is forbidden and will be
prosecuted by law. By accessing this system, you agree that your
actions may be monitored.
****************************************************************************


debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/developer/.ssh/identity
debug1: Trying private key: /home/developer/.ssh/id_rsa
debug1: Trying private key: /home/developer/.ssh/id_dsa
debug1: Next authentication method: password
debug1: read_passphrase: can't open /dev/tty: No such device or address
ssh_askpass: exec(/usr/libexec/openssh/ssh-askpass): No such file or directory
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: No such device or address
ssh_askpass: exec(/usr/libexec/openssh/ssh-askpass): No such file or directory
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: No such device or address
ssh_askpass: exec(/usr/libexec/openssh/ssh-askpass): No such file or directory
debug1: Authentications that can continue: publickey,password
debug1: No more authentication methods to try.
Permission denied (publickey,password).

Answer 1

我有这个read_passphrase：当我的私钥被错误地格式化时，无法打开 /dev/tty错误-而不是许多行，它是作为一行程序传递的，并且您可能有任何其他格式问题，如开始时忘记的"-"结束，或者行尾有错误，比如缺少换行符格式或行尾有一个附加字母。

请参阅Dockerfile:clone repo with passwordless private key。错误：“authentication agent”或“read_passphrase:can't open/dev/tty”了解更多详细信息，其主要思想是在docker文件中向ssh代理添加私钥，这同样是Gitlab CI/docker的思想：ssh Add不断请求密码。

Answer 2

从错误日志：

可以继续的身份验证：公钥、密码

由于您没有公钥设置（“没有id_rsa”），因此需要输入密码才能访问远程服务器，但您已断开了stdin:

读取\u密码：无法打开/dev/tty:没有这样的设备或地址

SSH不太适合黑客自动输入密码，因此如果您不能在上面放置id_rsa，最好的办法是在输入远程服务器的密码后进行后台处理并分离。试试^Z：

1. 运行nohup nohupssh。嘘