Thanks for the tip, I was not aware of it.
I did finally fix this issue. The problem was missing /dev/pts support in the kernel. What's really strange is that ssh was working on the host system but not inside the vservers, but after enabling /dev/pts, everything worked..
Anyhow, thanks everyone for the help!
--
Cedric
On Mon, 2004-03-15 at 15:10, Sam Vilain wrote:
Use sshd -t -p NNN (where NNN is a port number) inside the vserver. then ssh -v -p NNN yourhost All will be revealed. If you don't even see the daemon process do anything, then you have a more basic firewalling / routing / etc issue. `tcpdump' and `netstat -plunt' are also highly recommended. Sam. On Sat, 13 Mar 2004 06:02, Cedric Veilleux wrote; > Thanks for the hint, but unfortunately, even after restarting sshd, I > still have the same problem. > > > Thank you. > > -- > Cedric Veilleux > > > On Fri, 2004-03-12 at 11:39, Gregory (Grisha) Trubetskoy wrote: > > > 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 > > > > >
