"Error en la request de asignación de PTY en el canal 2" durante el uso de SSH

Estos días, cuando trato de SSH a mi server me sale este error:

PTY allocation request failed on channel 2 

Solía ​​SSH a ese server durante aproximadamente 2 años.

¿Qué pasó con mi SO (OS X lion) esta semana que causó este problema?

file de logging para: ssh -vvv user @ XXXX

 OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /etc/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to XXXX [XXXX] port 22. debug1: Connection established. debug1: identity file /Users/AR/.ssh/id_rsa type -1 debug1: identity file /Users/AR/.ssh/id_rsa-cert type -1 debug1: identity file /Users/AR/.ssh/id_dsa type -1 debug1: identity file /Users/AR/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3 debug1: match: OpenSSH_4.3 pat OpenSSH_4* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 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 debug2: dh_gen_key: priv key bits set: 131/256 debug2: bits set: 532/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: check_host_in_hostfile: host XXXX filename /Users/AR/.ssh/known_hosts debug3: check_host_in_hostfile: host XXXX filename /Users/AR/.ssh/known_hosts debug3: check_host_in_hostfile: match line 1 debug1: Host 'XXXX' is known and matches the RSA host key. debug1: Found key in /Users/AR/.ssh/known_hosts:1 debug2: bits set: 506/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /Users/AR/.ssh/id_rsa (0x0) debug2: key: /Users/AR/.ssh/id_dsa (0x0) debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-with-mic,password debug3: prefernetworking publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining prefernetworking: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /Users/AR/.ssh/id_rsa debug3: no such identity: /Users/AR/.ssh/id_rsa debug1: Trying private key: /Users/AR/.ssh/id_dsa debug3: no such identity: /Users/AR/.ssh/id_dsa debug2: we did not send a packet, disable method debug3: authmethod_lookup password debug3: remaining prefernetworking: ,password debug3: authmethod_is_enabled password debug1: Next authentication method: password USER@XXXX's password: debug3: packet_send2: adding 48 (len 61 padlen 19 extra_pad 64) debug2: we sent a password packet, wait for reply debug1: Authentication succeeded (password). Authenticated to XXXX ([XXXX]:22). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Entering interactive session. debug2: callback start debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug1: Sending environment. debug3: Ignonetworking env TERM_PROGRAM debug3: Ignonetworking env TERM debug3: Ignonetworking env SHELL debug3: Ignonetworking env TMPDIR debug3: Ignonetworking env Apple_PubSub_Socket_Render debug3: Ignonetworking env TERM_PROGRAM_VERSION debug3: Ignonetworking env TERM_SESSION_ID debug3: Ignonetworking env USER debug3: Ignonetworking env COMMAND_MODE debug3: Ignonetworking env SSH_AUTH_SOCK debug3: Ignonetworking env __CF_USER_TEXT_ENCODING debug3: Ignonetworking env PATH debug3: Ignonetworking env PWD debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug3: Ignonetworking env SHLVL debug3: Ignonetworking env HOME debug3: Ignonetworking env LOGNAME debug3: Ignonetworking env DISPLAY debug3: Ignonetworking env SECURITYSESSIONID debug3: Ignonetworking env _ debug2: channel 0: request shell confirm 1 debug2: fd 3 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel_input_status_confirm: type 100 id 0 PTY allocation request failed on channel 0 

  • ¿Cómo activo X-forwarding en OSX Lion?
  • ShellShock: ¿Debo preocuparme por esto en OS X Mavericks?
  • ¿Qué puedo hacer cuando mi session SSH está bloqueada?
  • Wake On Lan Sleeping Mac Problemas
  • Terminal Actived Push Notification Utility para OS X e iOS?
  • Establezca iTerm2 como el manejador de URL ssh: //
  • El file de identidad no funciona
  • ¿Cómo desbloquear mi mac de forma remota?
  • One Solution collect form web for “"Error en la request de asignación de PTY en el canal 2" durante el uso de SSH”

    No estoy seguro si ese problema aún existe, pero al preguntar a The-Big-G tuve la printing de que puede tener un problema con el assembly del sistema de files PTS en / etc / fstab en el server:

    la request de asignación pty falló – 1ra.

    la request de asignación pty falló – 2nd

    la request de asignación pty falló – 3ra.

    Revisé cuatro respuestas y todas dicen lo mismo: un problema con / dev / pts en el server

    Por supuesto, en teoría, nadie debería poder conectarse. Pero, después de todo, son computadoras y, a menudo, no hay lógica involucrada 🙂

    Loving Apple Products like poisoning (iPhone, iPad, iMac, Macbook, iWatch).