OpenSolaris

Printable Version Enter a New Search
Bug ID 6238952
Synopsis solaris 10/nevada: 4624458 seems to be back
State 10-Fix Delivered (Fix available in build)
Category:Subcategory ldap:switch
Keywords duckwater | dwp0 | onnv_triage | rpe-reviewed
Responsible Engineer Tomas Heran
Reported Against
Duplicate Of
Introduced In solaris_9
Commit to Fix snv_93
Fixed In snv_93
Release Fixed solaris_nevada(snv_93)
Related Bugs 4624458 , 6712098 , 5014922 , 6226776 , 6238255
Submit Date 10-March-2005
Last Update Date 3-July-2008
Description
While investigating escalated CR 6226776 and trying to reproduce it on a recent build of nevada, I realized that nevada (and probably s10 also) might hit 4624458 (if hostname is used in NS_LDAP_SERVERS, ldap goes into loop) again. 

A simple test tend to confirm this on snv_09: 

1. configure a nevada native LDAP client to use a profile where default/preferred servers list only has IP addresses. Works OK.
2. same as 1., but default/preferred servers list contains hostname that can be resolved in ldap only. ldapclient init fails.
3. same as 2, making sure that hostnames can be resolved in files (and before ldap) for instance. Works OK.
3. same as 3. Then comment the line in /etc/hosts that resolves the LDAP server hostname, and reboot. LDAP users can not then connect to the LDAP client, and such messages are displayed on the console:

svc.startd[7]: svc:/network/ldap/client:default: Method or service exit timed out.  Killing contract 30.

and eventually ldap service is put in maintenance:

# svcs -x svc:/network/ldap/client:default
svc:/network/ldap/client:default (LDAP client)
 State: maintenance since Thu Mar 10 18:36:00 2005
Reason: Start method failed repeatedly, last died on Killed (9).
   See: http://sun.com/msg/SMF-8000-KS
   See: ldap_cachemgr(1M)
   See: /var/svc/log/network-ldap-client:default.log
Impact: This service is not running.
#


pstack on ldap_cachmgr before it is killed gives:

# pstack 152
152:    /usr/lib/ldap/ldap_cachemgr
-----------------  lwp# 1 / thread# 1  --------------------
 ff23f4ec pause    ()
 00012924 main     (1, 17400, 1, 4, 2c680, 2a800) + 5d0
 00012024 _start   (0, 0, 0, 0, 0, 0) + 108
-----------------  lwp# 2 / thread# 2  --------------------
 ff23feb4 door     (fec79f08, 1fe8, 0, 0, fec7bfa0, 4)
-----------------  lwp# 3 / thread# 3  --------------------
 ff23fe78 door     (0, feb7bf90, 0, fecd0000, ff266274, 8)
 ff23e750 _lwp_start (0, 0, 0, 0, 0, 0)
-----------------  lwp# 4 / thread# 4  --------------------
 ff238274 mutex_unlock (2c4f0, 1000, ff26ab80, fecd0400, 2c4f8, 0) + 178
 00016f88 getldap_refresh (0, 2c400, 2be44, 2c678, 0, 1) + 54
 ff23e750 _lwp_start (0, 0, 0, 0, 0, 0)
-----------------  lwp# 5 / thread# 5  --------------------
 ff23e7f0 lwp_park (0, fe97be60, 0)
 ff238ac4 cond_wait_queue (2c4d8, 2c4c0, fe97be60, 0, 0, 0) + 28
 ff238f3c cond_wait_common (2c4d8, 2c4c0, fe97be60, 0, 0, 0) + 298
 ff2390d4 _cond_timedwait (2c4d8, 2c4c0, 2c4e8, fffffff8, ffffffe0, 0) + 34
 ff2391c8 cond_timedwait (2c4d8, 2c4c0, 2c4e8, 1000, 0, 0) + 14
 00016130 ???????? (3, 2c4c0, 1, 14, 2c400, 0)
 00016368 getldap_serverInfo_refresh (0, fe97c000, 0, 3, 2, 0) + 44
 ff23e750 _lwp_start (0, 0, 0, 0, 0, 0)
-----------------  lwp# 7 / thread# 7  --------------------
 ff23feb4 door     (0, 0, 0, 0, fe77bfa0, 4)
-----------------  lwp# 8 / thread# 8  --------------------
 ff23feb4 door     (0, 0, 0, 0, fe67bfa0, 4)
-----------------  lwp# 9 / thread# 9  --------------------
 ff23feb4 door     (fe579f08, 1fe8, 0, 0, fe57bfa0, 4)


 xxxxx@xxxxx.com 2005-03-10 17:43:15 GMT
Work Around
make sure that the hostname can be resolved by another repository (files for instance) before ldap.
 xxxxx@xxxxx.com 2005-03-10 17:43:16 GMT
Comments
N/A