Have you tried restarting sshd after starting vserver: # vserver blah exec service sshd restart [or whatever the command may be for your Linux distro]
I'm curious if this is a similar problem to what I saw (see messages from last week) with permission denied to pts/X (X is a number). For me restarting sshd fixed the problem, though I still don't know what the problem is and would like to have it solved. Grisha On Fri, 12 Mar 2004, Cedric Veilleux wrote: > Hi, > > After upgrading from an old-world 2.4.20ctx-17 to 2.4.25-vs1.26, I > can no longer login to an SSH server running inside a vserver. > > Beside the change to the host server, nothing has changed with the > virtual server. > > When login in with openssh's ssh client, it just hangs there > indifinately after asking for the password. When login with putty, I get > the message "Server refused to allocate pty". > > I tried to change the shell of the user of the vserver from bash to > sash (static shell), and I was able to login into a somehow broken > shell. Here's the output of me logging in and then typing the 'w' > command: > > ------------------------------------------------------------------------ > bash-2.05b$ ssh [EMAIL PROTECTED] > [EMAIL PROTECTED]'s password: > $ readline: warning: rl_prep_terminal: cannot get terminal settings > 11:22:53 up 3 days, 20:43, 0 users, load average: 0.00, 0.00, 0.00 > > USER TTY FROM > LOGIN@ IDLE JCPU PCPU WHAT > $ readline: warning: > rl_prep_terminal: cannot get terminal settings > ------------------------------------------------------------------------ > > I did some research on the "rl_prep_terminal: cannot get terminal > settings" error message, but didn't find anything. > > I checked if the proper devices were setup inside the vserver. I am > not sure what should be there, but I haven't changed anything and it did > work before the upgrade.. > > Content of /dev: > ------------------------------------------------------------------------ > crw-rw-rw- 1 root root 1, 7 Dec 21 2002 full > prw------- 1 root root 0 Mar 10 14:31 initctl > srw-rw-rw- 1 root root 0 Mar 10 15:00 log > crw-rw-rw- 1 root root 1, 3 Dec 21 2002 null > crw-rw-rw- 1 root root 5, 2 Dec 21 2002 ptmx > drwxr-xr-x 2 root root 192 Mar 11 01:18 pts > crw-r--r-- 1 root root 1, 8 Dec 21 2002 random > crw-rw-rw- 1 root root 5, 0 Mar 10 14:55 tty > crw-r--r-- 1 root root 1, 9 Dec 19 01:07 urandom > crw-rw-rw- 1 root root 1, 5 Dec 21 2002 zero > ------------------------------------------------------------------------ > > Content of /dev/pts: > ------------------------------------------------------------------------ > crw--w---- 1 root tty 136, 0 Mar 11 01:18 0 > crw--w---- 1 root tty 136, 1 Mar 10 23:59 1 > crw--w---- 1 root tty 136, 2 Mar 10 23:59 2 > crw--w---- 1 root tty 136, 3 Mar 10 15:38 3 > crw--w---- 1 root tty 136, 5 Mar 10 16:15 5 > crw--w---- 1 root tty 136, 6 Mar 10 16:15 6 > ------------------------------------------------------------------------ > > > I have not granted any additional capabilities to the vserver. > > > As you can see I have tried everything I could. I just can't figure > out what's the problem. Besides sshd, everything works flawlessly inside > the vserver (apache, syslog, cron, xinetd+vsftpd). > > > Any help greatly appreciated! > > -- > C?dric Veilleux > > _______________________________________________ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver > _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
