The point was to use ps on the *server* not on the client.
So I was thinking you should use ps *on that server* to
see if you could see signs of another connection attempt reaching it
and then for some reason failing to give you an interactive shell.
Ah ok. Yes I totally misunderstood you- I
On Sun, Aug 2, 2015 at 7:02 AM, Quartz wrote:
> I know how ps works :)
Ok, good, then the problem lies elsewhere...
> On OSX, an outbound ssh connection spawns a single 'ssh' process, which is a
> child of bash. bash is a child of login. login is a child of Terminal.
Perhaps here.
The point wa
Exactly. Probably ps -l (or maybe install and use pstree). Do you get
new processes with sshd as a parent?
I never get that. When ssh-ing into another machine I just get a single ssh
process that's a direct child of the bash for that tty, there's never an
sshd anywhere.
When you use ps -l you
On Sat, Aug 1, 2015 at 6:53 PM, Quartz wrote:
>> Exactly. Probably ps -l (or maybe install and use pstree). Do you get
>> new processes with sshd as a parent?
>
> I never get that. When ssh-ing into another machine I just get a single ssh
> process that's a direct child of the bash for that tty,
good day:
"ssh user@server" = works just like it should
What about "ssh -v user@server" on a good day?
That works exactly as expected. ssh-ing in right now
And more specifically, if
you run ssh -v on both a good day and a bad day, what does diff between
the two outputs show?
IIRC, not muc
Thus said Quartz on Sat, 01 Aug 2015 19:00:56 -0400:
> good day:
> "ssh user@server" = works just like it should
What about "ssh -v user@server" on a good day? And more specifically, if
you run ssh -v on both a good day and a bad day, what does diff between
the two outputs show?
Andy
--
TAI64
If you are only creating one ssh connection, does "good day" mean you
have succeeded just once?
No, I mean that I can ssh in without having to pass -v on the command
line. In other words, it works the way it normally should.
More specifically:
good day:
"ssh user@server" = works just like it
ktrace and tcpdump.
I should have mentioned that the laptop is using OpenSSH but it's OSX
not OpenBSD. ktrace was replaced with I think dtrace on OSX a while ago,
so I'll have to look into how to get that set up.
As for tcpdump, I'm not sure what I'd be looking for there. Most of the
connection
That's a good question, I'm not actually sure if I've ever opened two
connections to it at once. For better or worse today is a "good" day so I'll
have to wait to test this.
If you are only creating one ssh connection, does "good day" mean you
have succeeded just once?
No, I mean that I can ss
Quartz wrote:
> > ktrace and tcpdump.
>
> I should have mentioned that the laptop is using OpenSSH but it's OSX
> not OpenBSD. ktrace was replaced with I think dtrace on OSX a while ago,
> so I'll have to look into how to get that set up.
>
> As for tcpdump, I'm not sure what I'd be looking for
On Sat, Aug 1, 2015 at 10:58 AM, Quartz wrote:
> That's a good question, I'm not actually sure if I've ever opened two
> connections to it at once. For better or worse today is a "good" day so I'll
> have to wait to test this.
If you are only creating one ssh connection, does "good day" mean you
ktrace and tcpdump.
I should have mentioned that the laptop is using OpenSSH but it's OSX
not OpenBSD. ktrace was replaced with I think dtrace on OSX a while ago,
so I'll have to look into how to get that set up.
As for tcpdump, I'm not sure what I'd be looking for there. Most of the
connec
If you have one connection established to that server which is
functioning (perhaps with -v on the client ssh) can you get the
problem to occur with a second connection to that server?
That's a good question, I'm not actually sure if I've ever opened two
connections to it at once. For better or
Quartz wrote:
> Searching the web for info is worthless because the first thing
> everybody tells you to do when debugging a connection issue is enable
> verbose, which obviously doesn't help me here. Likewise, I can't even
> confirm if anyone else has even experienced this sort of failure befor
If you have one connection established to that server which is
functioning (perhaps with -v on the client ssh) can you get the
problem to occur with a second connection to that server?
If so, can you take a look at whether you are getting any fresh
processes from your second connection attempts wh
I'm not sure if this is the right place to ask about this, but I can't
seem to find an ssh-specific mailing list or web forum anywhere.
I have a bog standard setup between a laptop and a local university that
uses a bog standard id_rsa key for password-less access; to the best of
my knowledge
16 matches
Mail list logo
