From: Sam Vilain (sam.vilain_at_paradise.net.nz)
Date: Mon 15 Mar 2004 - 07:10:27 GMT
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
> >
>
>
>
-- Sam Vilain, sam /\T vilain |><>T net, PGP key ID: 0x05B52F13 (include my PGP key ID in personal replies to avoid spam filtering)"That man is richest whose pleasures are cheapest" - Thoreau -
_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver