This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 155100

Summary: Zombie sshd process remains after the end of ssh session
Product: [Fedora] Fedora Reporter: Vovchik Vovkovich <noth>
Component: opensshAssignee: Tomas Mraz <tmraz>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-29 08:39:32 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Vovchik Vovkovich 2005-04-16 04:52:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
When working with server via ssh, after logout got zombie shell and sshd processes. These zombie processes stay for a long time and they can be killed by "kill -9" command. 

Version-Release number of selected component (if applicable):
openssh-3.9p1-8.0.1

How reproducible:
Sometimes

Steps to Reproduce:
1. Log in to server over ssh
2. Log off

  

Actual Results:  Sometimes zombie processes of shell and sshd appear.

Expected Results:  There should be no session processes after logout.

Additional info:

After logout of user "qwert" following processes remain

[root@host /]# ps aux | grep qwert

root      8305  0.0  0.1  6900 1868 ?        Ss   08:38   0:00 sshd: qwert[priv]
qwert     8318  0.0  0.1  7104 2016 ?        S    08:39   0:00 sshd: qwert@pts/8
qwert     8319  0.0  0.0     0    0 ?        Zs   08:39   0:00 [bash] <defunct>
root     24662  0.0  0.0  5144  696 pts/9    S+   15:48   0:00 grep qwert
Comment 1 Tomas Mraz 2005-04-18 03:36:51 EDT
I cannot reproduce this bug here.

Does it happen even if you connect to the machine and logout immediately?

Which ssh client do you use? And could you try to reproduce the problem using
various ssh clients?

Also you could try to rebuild the openssh-4.0p1-2 from Fedora Core Development
and install it on your machine and try if it solves the problem or not.
Comment 2 Tomas Mraz 2005-06-29 08:39:32 EDT
I cannot reproduce it and reporter doesn't respond.