Bug 210916 - Admin Server doesn't start on RHEL3 - libldap60.so + sasl
Summary: Admin Server doesn't start on RHEL3 - libldap60.so + sasl
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Admin
Version: 1.0.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: fds103trackingbug
TreeView+ depends on / blocked
 
Reported: 2006-10-16 15:25 UTC by Rich Megginson
Modified: 2015-12-07 17:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-07 17:00:05 UTC
Embargoed:

Attachments (Terms of Use)
diffs for fix (2.43 KB, patch)
2006-10-16 15:25 UTC, Rich Megginson 		no flags Details | Diff
View All

Description Rich Megginson 2006-10-16 15:25:59 UTC 
The Admin Server doesn't start on RHEL3 with the new libldap60.so because it
doesn't know how to resolve the SASL dependency.  This is not a problem on RHEL4
and FC because httpd is linked directly with libsasl2.so
Comment 1 Rich Megginson 2006-10-16 15:25:59 UTC 
Created attachment 138584 [details]
diffs for fix
Comment 2 Nathan Kinder 2006-10-16 15:47:29 UTC 
Looks good.
Comment 3 Rich Megginson 2006-10-16 15:57:45 UTC 
Reviewed by: nkinder (Thanks!)
Files: see diff
Branch: HEAD
Fix Description: Adding libldap60.so to the LD_PRELOAD solves the problem. 
Loading libldap60.so early forces the dynamic linker to find and resolve
libsasl2.so.  So I modified start-admin to do the LD_PRELOAD of libldap60.  I
also updated the patch file which is used when upgrading 1.0.2 to 1.0.3.
Platforms tested: RHEL3
Flag Day: no
Doc impact: no 

Checking in start-admin;
/cvs/dirsec/adminserver/admserv/cfgstuff/start-admin,v  <--  start-admin
new revision: 1.7; previous revision: 1.6
done
Checking in adminserver-start-admin.patch;
/cvs/dirsec/adminserver/admserv/cfgstuff/adminserver-start-admin.patch,v  <-- 
adminserver-start-admin.patch
new revision: 1.4; previous revision: 1.3
done
Note You need to log in before you can comment on or make changes to this bug.