Another observation :
running this command :
watch -n 1 date
on two difference ssh-conntection to two different servers continously show the
running date and time.
The time is of cause offset by some amount of seconds (20 in my case).
Based on that offset I can see that those two connections
** Attachment added: sshd running on port 2022. Dropping connection after a
while
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/716310/+attachment/1849580/+files/sshd.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Soren, I just now re-read your original description, and I see this:
debug1: Killed by signal 15.
That suggests that your *client* ssh is being killed.
The sshd debug supports that:
debug3: fd 9 is O_NONBLOCK
debug1: Setting controlling tty using TIOCSCTTY.
Received disconnect from
Clint - I owe you beer or something. I develop machine-control software,
and apparently the exit procedure of our application is to kill all ssh-
client - since our application creates some ssh-tunnels. I was not aware
of that until your hit about something must be killed my ssh.
Thanks your very
ssh was killed by non ubuntu app.
** Changed in: openssh (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/716310
Title:
ssh connections
On Mon, 2011-02-14 at 21:13 +, Søren Holm wrote:
Clint - I owe you beer or something. I develop machine-control software,
and apparently the exit procedure of our application is to kill all ssh-
client - since our application creates some ssh-tunnels. I was not aware
of that until your hit
Ok on another server I administer :
sgh@zemeckis:~$ sudo status ssh
ssh stop/waiting
sgh@zemeckis:~$ cat /var/run/sshd.pid
11889
sgh@zemeckis:~$
that is not good I guess? since I did the login over ssh.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
$ ls -al /var/run/sshd.pid
-rw-r--r-- 1 root root 5 2011-02-09 22:13 /var/run/sshd.pid
$ sudo status ssh
ssh start/running, process 1019
$
Why/how could bug #531912 make my connections disconnect ?
Using another ssh client (fx putty) does not disconnect.
--
You received this bug
Oops, I also meant to ask you to cat the /var/run/sshd.pid to make sure
it is in fact the same as the one in status.
My suspicion is/was that the upstart managed sshd is conflicting with a
/etc/init.d/ssh managed sshd. On second thought I'm not so sure.
Can you try running an sshd in debug mode
Hello Soren, can you please check to see if you have the file
/var/run/sshd.pid
and also run the command
sudo status ssh
If you do have the pid file, this may be a duplicate of bug #531912
Marking Incomplete pending response from Soren.
** Changed in: openssh (Ubuntu)
Status: New =
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/716310
Title:
ssh connections disconnects automatically
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
I can add that putty on linux does not disconnect.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/716310
Title:
ssh connections disconnects automatically
--
Ubuntu-server-bugs
12 matches
Mail list logo
