summaryrefslogtreecommitdiff
path: root/open_issues/ssh_pty_allocation_request_failed.mdwn
blob: af9e71351c5f783f7abb17915c2bac9aeae48d32 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
[[!meta copyright="Copyright © 2018 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!meta title="SSH: PTY allocation request failed"]]

Occasionally seen when `ssh`ing to a Hurd system:

    $ ssh [...]
    PTY allocation request failed on channel 0
    GNU laplace 0.9 GNU-Mach 1.8+git20180218-486-dbg/Hurd-0.9 i686-AT386
    This is the GNU Hurd.  Welcome.  [...]
    [No prompt displayed.]
    [C-d]
    Connection to [...] closed.

That is, we failed to get a PTY allocated.

We currently set up a limited number of translator nodes providing preallocated
PTYs ([[hurd/translator/term]] translator instances), instead of dynamically
allocating via `/dev/ptmx`, for example.
(Which might or might not resolve this issue; there might be some resource leak
involved?)

Last seen timestamp: 2018-07 (lost exact date).