Bug 54157 - nss_ldap problems with multiple SSH (R) client windows
Summary: nss_ldap problems with multiple SSH (R) client windows
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openssh
Version: 7.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-28 21:34 UTC by John Dalbec
Modified: 2008-05-01 15:38 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-09-28 21:34:52 UTC


Attachments (Terms of Use)

Description John Dalbec 2001-09-28 21:34:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (Windows NT 5.0; U)

Description of problem:
My account is defined only to LDAP and not on the /etc files (recent change).  Also I recently upgraded tux, mkinitrd, filesystem, setup, 
e2fsprogs(-devel), and bash to Roswell because I'm looking for a kernel without long NFS write latencies (2.4.3) and without kupdated 
lockups on ReiserFS (2.4.7).  When I connect with the SSH(R) windows client, I'm OK as long as I have only one window open.  As soon 
as I try to open a second terminal window, I get disconnected.  If I run separate copies of the client, that's OK too.  If I alternate between 
terminal and file-transfer windows, I'm OK.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Install RH 7.1
2.Set up LDAP authorization
3.Sign on using SSH(R) Windows client as LDAP-only user
4.Open second terminal window
	

Actual Results:  Server disconnects.

Expected Results:  Second terminal window opens, executes new bash instance.

Additional info:

Sep 28 17:22:27 mail01 sshd[5283]: nss_ldap: could not get LDAP result - Can't contact LDAP server
Sep 28 17:22:27 mail01 sshd[5283]: nss_ldap: could not get LDAP result - Can't contact LDAP server
Sep 28 17:22:27 mail01 sshd[5283]: fatal: PAM session setup failed[14]: Cannot make/remove an entry for the specified session

The LDAP server is fine, or I wouldn't be able to log in in the first place.

Comment 1 John Dalbec 2001-10-02 14:21:15 UTC
D'oh! Upgrading nss_ldap to Roswell (requires upgrading db3 and openssl also) fixed the problem.


Note You need to log in before you can comment on or make changes to this bug.