我正在改变我的dedi框上的一些设置来添加更多的描述符，然后重新启动。 从那以后，我无法用root的细节（或其他任何人）loginSSH。 只要我login，腻子屏幕closures。 当我从我的其他VPS ssh [email protected] ，它login然后说连接closures。
我现在真的坚持了，因为我已经失去了我的服务器的shell访问，只有plesk ..
编辑：从ssh -v详细输出
debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to domain [IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type 2 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 debug1: Host 'domain' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 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-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information Unknown code krb5 195 debug1: Unspecified GSS failure. Minor code may provide more information Unknown code krb5 195 debug1: Unspecified GSS failure. Minor code may provide more information Unknown code krb5 195 debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Offering public key: /root/.ssh/id_dsa debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: password root@domain's password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. Last login: Tue Jun 14 00:05:36 2011 from 02dc9b0a.bb.sky.com debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 Connection to domain closed. debug1: Transferred: stdin 0, stdout 0, stderr 35 bytes in 0.3 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 106.5 debug1: Exit status 254
有任何想法吗？
凯尔肯定是有一件事 – 你的shell没有被正确的产生。 但是退出状态让我觉得这是一个shell本身的问题，而不是机器无法分叉的过程。
如果我不得不猜测，我会说你的shell已被禁用 – 可能通过将其设置为/ bin / false或类似的。
你的系统实际上可能已经超过了允许进程的数量，这将导致sshd无法产生你的shell。 我不熟悉Plesk，你能用它来阻止麻烦制造者的服务吗？