通过ssh登录我的某个服务器时,它只是在身份验证后挂起.这是客户端上带-v的输出.
OpenSSH_4.3p2,OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to host1 [10.6.27.64] port 22. debug1: Connection established. debug1: identity file /home/user/.ssh/identity type -1 debug1: identity file /home/user/.ssh/id_rsa type 1 debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: loaded 3 keys debug1: Remote protocol version 2.0,remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.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 debug1: Host 'host1' is known and matches the RSA host key. debug1: Found key in /home/user/.ssh/known_hosts:172 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 debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Unspecified GSS failure. Minor code may provide more information No credentials cache found debug1: Next authentication method: publickey debug1: Trying private key: /home/user/.ssh/identity debug1: Offering public key: /home/user/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = C debug1: Sending env LC_ALL = C Last login: Wed May 21 10:24:14 2014 from host2 This machine has been configured with kickstart host1 in bcinf17 in bay 3 in rack D10-Mid
在服务器上的/ var / log / secure中我看到了这一点(幸运的是我仍然打开了一个会话)：
May 21 10:27:31 host1 sshd[12387]: Accepted publickey for user from 1.1.11.239 port 34135 ssh2 May 21 10:27:31 host1 sshd[12387]: pam_unix(sshd:session): session opened for user user by (uid=0)
所以没有明显的错误.客户端和服务器似乎能够进行通信. / var / log / messages中没有任何内容.
充足的磁盘空间.安装了一些路径(包括家庭区域),但我仍然活跃的shell可以访问它们.
我可以连接到其他服务器;只有这一个有问题.我试过重启sshd. sshd的配置文件看起来像默认配置文件,因此没有任何内容.据我所知,最近没有任何变化.
尝试运行命令(ssh host1 -t bash或-t vi)似乎也挂起,所以不要认为它与我的登录脚本有任何关系.
还尝试从同一位置和其他位置的其他主机登录,或通过Putty从Windows登录,并使用密码而不是密钥登录.
不知道在哪里可以看到或者还有什么可以尝试.
这是一个64位的RHEL 6.4服务器.
解决方法
在SSH身份验证之后,有几件事可能导致挂起.
然而,其中大多数还会带来其他症状(SSH-auth之后的挂起只是最明显的症状)
>〜/ .bashrc,〜/ .bash_profile,〜/ .profile,〜/ .kshrc等等
>运行/重新启动的进程太多.
>有些东西有fork()’太多的子进程而且负载(the 1/5/15 score)太高了.
>存在I / O等待问题.
>通常由垂死的硬盘驱动器(通用)或性能不佳的NIC(罕见)引起.
>第三方PAM模块挂起(例如：非标准Kerberos配置)
>并不总是模块本身,但有时是一个服务(如审计),在某处有一个完整的日志服务器.
