Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

rlogind: Unable to allocate pty on remote host.

SOLVED
Go to solution
TalH
Advisor

rlogind: Unable to allocate pty on remote host.

Hi,
I increased the “npty” & “nstrpty” parameters from 60 to 120 and sam reports that the usage of npty is 0 and usage of nstrpty is 62 but still we get the “Unable to allocate pty on remote host”
The system is 11.31.
Any ideas?

Thanks!

Tal
8 REPLIES
Laurent Menase
Honored Contributor
Solution

Re: rlogind: Unable to allocate pty on remote host.

did you reboot?
check
# kctune -v nstrpty
# insf -v -d pts


TalH
Advisor

Re: rlogind: Unable to allocate pty on remote host.

Hi,

Thanks for the prompt response, and yes, the system is after restart.

this is the output i get:

# kctune -v nstrpty
Tunable nstrpty
Description Maximum number of Streams-based pseudo-terminals
Module ptm
Current Value 120
Value at Next Boot 120
Value at Last Boot 120
Default Value 60
Can Change At Next Boot Only

# insf -v -d pts
insf: Installing special files for pseudo driver pts

Thanks!

Tal
Laurent Menase
Honored Contributor

Re: rlogind: Unable to allocate pty on remote host.

try a
ls /dev/pts/[1-9a-zA-Z]* | wc
rlogind is using streams pty.
The other possibility is that you still have process owning the pts after the session end.
and ptm is closed.


TalH
Advisor

Re: rlogind: Unable to allocate pty on remote host.

# ls /dev/pts/[1-9a-zA-Z]* | wc
119 119 1419
Laurent Menase
Honored Contributor

Re: rlogind: Unable to allocate pty on remote host.

so orphaned pts.
you still have application opening them
or ptm side.
so probably lsof may give you the answer.
Rita C Workman
Honored Contributor

Re: rlogind: Unable to allocate pty on remote host.

You know...I always thought there were 3 you needed to adjust:
npty;
nstrpty; and

nstrtel - the number of telnet devices files the kernel can support for incoming telnet sesssions.

Just thinking out loud,
Rita
Laurent Menase
Honored Contributor

Re: rlogind: Unable to allocate pty on remote host.

Hi Rita

npty -ptys driver -> bsd pty -> /dev/pty/tty*

nstrpty -streams pty -> /dev/pts/[:number:]

nstrtel -telnet pty ->/dev/pts/t*

They are all separate


Laurent Menase
Honored Contributor

Re: rlogind: Unable to allocate pty on remote host.

if you didn't solve it, you may need to open a call to hp support