Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 432070

Summary: bad definition of ServerIPAddress makes setup-ds-admin.pl segfault
Product: Red Hat Directory Server Reporter: Chris Duryee <cduryee>
Component: Install/UninstallAssignee: Nathan Kinder <nkinder>
Status: CLOSED DUPLICATE QA Contact: Chandrasekar Kannan <ckannan>
Severity: low Docs Contact:
Priority: medium    
Version: 8.0CC: benl, nhosoi, nmalik
Target Milestone: DS8.1   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-28 23:49:30 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:
Bug Depends On:    
Bug Blocks: 249650    
Attachments:
Description Flags
program to reproduce the problem none

Description Chris Duryee 2008-02-08 17:55:24 UTC 
Description of problem:

From an email:

>
It looks like there is a problem with the way we handle ServerIPAddress in
setup-ds-admin.pl.  It is only necessary to provide this value in your .inf if
you have a machine that has multiple IP addresses and you want it to listen on
only 1 of those.  The default is to listen on all interfaces.  If you really
need to listen to only 1 IP address, for now you'll have to edit console.conf
after running setup-ds-admin.pl and change the Listen directive manually.

The problem on this machine is that the hostname is configured to be
nmalik-ldap, but for some reason calling PR_GetHostByName with nmalik-ldap
returns NULL.  If you use nmalik-ldap.usersys.redhat.com it works, but that's
not what PR_GetSystemInfo(PR_SI_HOSTNAME) returns. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Rich Megginson 2008-02-08 18:00:32 UTC 
Created attachment 294388 [details]
program to reproduce the problem
Comment 2 Rich Megginson 2008-02-08 18:02:24 UTC 
Looks like the code in validate_addr() in adminserver/admserv/cgi-src40/config.c
is incorrect, both the logic and the error checking.
Comment 5 Nathan Kinder 2009-01-28 23:49:30 UTC 
The logic used in validate_addr() has been changed by the fix for bug 430364.  There is no need for the validation code to be concerned with the hostname.  The validation now simply ensures that the requested address is available on the system by trying to bind it to a socket.

*** This bug has been marked as a duplicate of bug 430364 ***