Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Server refused to allocate pty

  1. #1
    Join Date
    May 2007
    Posts
    7

    Default Server refused to allocate pty

    I 'm getting a "Server refused to allocate pty" when trying to SSH in.

    The only semi-weird thing I've done is to do a full yum update of FC6 (but excluding kernel, udev, etc.) I am fairly sure I restarted after doing that a few weeks ago though when I first setup the VPS and I have been having no problems until now.

    Any help is appreciated. I've rebooted the server via the control panel. I have a limited backdoor to a command shell via webmin. I'm not really sure what else to try right now. I'm not even sure if this is actually a Fedora problem, or something with OpenVZ. I've seen posts on the OpenVZ forums related to this error message.

    Possibly relevant info:

    Code:
    > cat /proc/user_beancounters
    Version: 2.5
           uid  resource           held    maxheld    barrier      limit    failcnt
        52226:  kmemsize        1988119    2432786   14790793   15569256          0
                lockedpages           0          0        512        512          0
                privvmpages       12813      35880      59441      59441          0
                shmpages           1443       3379      25600      25600          0
                dummy                 0          0          0          0          0
                numproc              27         29        320        320          0
                physpages          8537      21407          0 2147483647          0
                vmguarpages           0          0      59441 2147483647          0
                oomguarpages       8537      21407      52428 2147483647          0
                numtcpsock           11         15        512        512          0
                numflock              1          4        512        512          0
                numpty                0          0         32         32          0
                numsiginfo            0         30        512        512          0
                tcpsndbuf        108780     275280    1342177    2684354          0
                tcprcvbuf        166412     189456    1342177    2684354          0
                othersockbuf      23736      68460    1342177    2684354          0
                dgramrcvbuf           0       8364     671088    1342177          0
                numothersock         21         33        512        512          0
                dcachesize       189956     216370    4026531    4026531          0
                numfile             780        884       8192       8192          0
                dummy                 0          0          0          0          0
                dummy                 0          0          0          0          0
                dummy                 0          0          0          0          0
                numiptent           260        260        768        768          0
    Code:
    > ls -la /dev
    total 8
    drwxr-xr-x  7 root root      820 May 26 02:24 .
    drwxr-xr-x 21 root root     4096 May 26 02:24 ..
    drwxr-xr-x  2 root root       60 May 26 02:24 .udev
    lrwxrwxrwx  1 root root       13 May 26 02:24 MAKEDEV -> /sbin/MAKEDEV
    lrwxrwxrwx  1 root root        4 May 26 02:24 X0R -> null
    crw-------  1 root root   5,   1 May 26 02:24 console
    lrwxrwxrwx  1 root root       11 May 26 02:24 core -> /proc/kcore
    lrwxrwxrwx  1 root root       13 May 26 02:24 fd -> /proc/self/fd
    prw-------  1 root root        0 May 26 02:24 initctl
    srw-rw-rw-  1 root root        0 May 26 02:24 log
    brw-r-----  1 root disk   7,   0 May 26 02:24 loop0
    brw-r-----  1 root disk   7,   1 May 26 02:24 loop1
    brw-r-----  1 root disk   7,   2 May 26 02:24 loop2
    brw-r-----  1 root disk   7,   3 May 26 02:24 loop3
    brw-r-----  1 root disk   7,   4 May 26 02:24 loop4
    brw-r-----  1 root disk   7,   5 May 26 02:24 loop5
    brw-r-----  1 root disk   7,   6 May 26 02:24 loop6
    brw-r-----  1 root disk   7,   7 May 26 02:24 loop7
    drwxr-xr-x  2 root root       40 May 26 02:24 mapper
    drwxr-xr-x  2 root root       60 May 26 02:24 net
    crw-rw-rw-  1 root root   1,   3 May 26 02:24 null
    crw-rw----  1 root lp    99,   0 May 26 02:24 parport0
    crw-rw----  1 root lp    99,   1 May 26 02:24 parport1
    crw-rw----  1 root lp    99,   2 May 26 02:24 parport2
    crw-rw----  1 root lp    99,   3 May 26 02:24 parport3
    crw-------  1 root root 108,   0 May 26 02:24 ppp
    drwxr-xr-x  2 root root        0 May 26 02:24 pts
    drwxr-xr-x  2 root root       40 May 26 02:24 shm
    brw-r--r--  1 root root   0, 233 May 26 02:24 simfs
    lrwxrwxrwx  1 root root       15 May 26 02:24 stderr -> /proc/self/fd/2
    lrwxrwxrwx  1 root root       15 May 26 02:24 stdin -> /proc/self/fd/0
    lrwxrwxrwx  1 root root       15 May 26 02:24 stdout -> /proc/self/fd/1
    crw-rw-rw-  1 root root   5,   0 May 26 02:24 tty
    crw--w----  1 root tty    4,   1 May 26 02:24 tty1
    crw--w----  1 root tty    4,   2 May 26 02:24 tty2
    crw--w----  1 root tty    4,   3 May 26 02:24 tty3
    crw--w----  1 root tty    4,   4 May 26 02:24 tty4
    crw--w----  1 root tty    4,   5 May 26 02:24 tty5
    crw--w----  1 root tty    4,   6 May 26 02:24 tty6
    -rw-r--r--  1 root root      512 May 26 02:24 urandom
    crw-rw-rw-  1 root root   1,   5 May 26 02:24 zero
    Code:
    > cat /etc/fstab
    none	/dev/pts	devpts	rw	0 0

    Any help is appreciated. I've restarted the server via the control panel once already.

  2. #2

    Default

    This sounds like something you should submit a support ticket for, if you haven't already!
    Kelvin Nicholson
    http://www.helomx.com - Blacklist and availability monitoring built from the ground up for outsourced IT providers.

  3. #3
    Join Date
    May 2006
    Location
    GMT +10
    Posts
    375

    Default

    I had exactly the same problem with CentOS when I did a big yum update recently.

    SSH died as a result of the yum update killing off several mount points that SSH needed.

    Try the solutions I used. Full story here:

    http://forums.vpslink.com/showthread.php?t=1569

  4. #4
    Join Date
    May 2007
    Posts
    7

    Default

    Thank you. Running these commands:

    /sbin/MAKEDEV pty
    /sbin/MAKEDEV tty

    ...allowed me to login via SSH again. I haven't checked yet if both of those are actually required, or only one of them is sufficient. In my case, SSHD was still running fine.

    However now, when I reboot, I get the same error and have to rerun the commands before I can SSH in again. I am not really familiar with udev and its friends, so I'll have to do some research . (Unless someone can say if there's an easy fix for this other than putting those commands in my rc.local.)

    The MAKEDEV commands created a lot of additional devices under /dev. Probably more than makes sense.

    Again thanks. At least I can SSH in now.

  5. #5
    Join Date
    May 2006
    Location
    GMT +10
    Posts
    375

    Default

    Good to hear it worked (sort of) for you.

    I hope yum doesn't get in the habit of doing this every time an update is done. That would be a real nuisance for all of us.

  6. #6
    Join Date
    Jun 2006
    Location
    Labrador, Canada
    Posts
    266

    Default

    Excuse a dumb question but if you couldn't login, how did you run those commands?
    D. Robbins
    vpsinfo : server status in your browser
    loadavg : lightweight load, memory & transfer monitoring

  7. #7
    Join Date
    May 2006
    Location
    GMT +10
    Posts
    375

    Default

    Webmin lets you run commands directly, without SSH. It sure helped me out.

  8. #8
    Join Date
    May 2007
    Posts
    7

    Default

    For anyone that runs across this... I still haven't figured out how to fix permanently except for calling /sbin/MAKEDEV explicitly. Everything I've looked at looks correct per what I've been reading.

    However, I did want to note that when I configured YUM update originally, I ignored kernel and udev, but I did not not ignore MAKEDEV. So, my best guess at this point is that MAKEDEV getting updated separately from the kernel (or maybe udev) is what caused the problem. I don't know how I could verify that without a lot of work or purchasing a new VPSLink and testing though. So, just fwiw.

    My current yum.conf looked like this previously:

    Code:
    exclude=udev kernel* mkinitrd module-init-tools
    and now looks like this:

    Code:
    exclude=udev kernel* mkinitrd module-init-tools MAKEDEV
    This is more inline with what another VPSLink user posted on the wiki regarding yum and Fedora. (He also ignored GCC packages, but I'm still not sure why.)

    Also fwiw, this is my current kernel headers, MAKEDEV, & udev library versions according to "rpm -qa":

    Code:
     kernel-headers-2.6.18-1.2798.fc6
     MAKEDEV-3.23-1.2
     udev-095-14

  9. #9
    Join Date
    Jul 2008
    Posts
    1

    Default

    Quote Originally Posted by kaliatech View Post
    Thank you. Running these commands:

    /sbin/MAKEDEV pty
    /sbin/MAKEDEV tty

    ...allowed me to login via SSH again. I haven't checked yet if both of those are actually required, or only one of them is sufficient. In my case, SSHD was still running fine.

    However now, when I reboot, I get the same error and have to rerun the commands before I can SSH in again. I am not really familiar with udev and its friends, so I'll have to do some research . (Unless someone can say if there's an easy fix for this other than putting those commands in my rc.local.)

    The MAKEDEV commands created a lot of additional devices under /dev. Probably more than makes sense.

    Again thanks. At least I can SSH in now.
    Thank you very much for this information, been looking for hours

  10. #10
    Join Date
    Oct 2008
    Posts
    1

    Default

    I had the same problem, I'm not really sure when it occurred or why. The fix you added worked just fine. I use WINSCP and open its terminal to add the commands, I don't know how it accessed the SSH but I used it for everything until I found this fix...

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •