Bug 166099

Summary:	pam_smb fails to try backup server
Product:	Red Hat Enterprise Linux 3	Reporter:	Cott Lang <cott>
Component:	pam_smb	Assignee:	Simo Sorce <ssorce>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	samba-bugs-list
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 18:56:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cott Lang 2005-08-16 22:11:23 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6

Description of problem:
I have two servers configured in my pam_smb.conf, PRIMARY and SECONDARY.

If PRIMARY and SECONDARY are both on the local subnet, either one can go down, and everything is fine, pam_smb appears to try one, then the other, and we're okay.

However, if the PRIMARY is on a different subnet, pam_smb hangs for a couple of MINUTES trying to access it, then times out and fails completely instead of attempting SECONDARY.

This is completely repeatable.


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

How reproducible:
Always

Steps to Reproduce:
1. secondary server on different subnet
2. fail primary server
3. try to login
  

Actual Results:  logins are impossible


Expected Results:  A faster timeout followed by failover to the backup server.


Additional info:

Comment 1 RHEL Program Management 2007-10-19 18:56:09 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.