Loading...
Loading...
On any HPE Integrity server running HP-UX/11.31 using LDAP-UX 05.04, the nss query – queries for passwd, group entries or other, i.e. getpwent(3C), getpwnam(3C),getgrnam(3C) pwget(1) -, and pam ldap authentication may stop responding with ldapclientd using 100% of the CPU on multiple CPUs, causing some application to stop responding./opt/ldapux/bin/ldapclientd using 100% on one or multiple CPUs is usually occurring when ldapclientd should coredump.This occurs under the following conditions:proxy user is expired or not valid:# /opt/ldapux/config/ldap_proxy_config -vFails and do NOT reply:File Credentials verified - validAndLDAP-UX is configured to use startTLS:# grep enable_startTLS /etc/opt/ldapux/ldapux_client.confenable_startTLS=1When those conditions are met, ldapclientd may then occasionally stop responding and use 100% of the CPU.
Any HPE Integrity server running HPUX 11iv3 and HPE LDAP-UX 05.X.
First, reconfigure any invalid or expired proxy user. Use the commands below for validation and restart ldapclientd once validated.# /opt/ldapux/config/ldap_proxy_config -v File Credentials verified - valid# /opt/ldapux/bin/ldapclientd -rIf fixing the proxy user issue does not address the unresponsiveness, configure LDAPUX to use LDAP over SSL port 636 in place of startTLS LDAP port 389. For example, use /opt/ldapux/config/setup to change "preferredServerList:" port and “LDAP_HOSTPORT_SSL” port from 389 to 636 and comment out "enable_startTLS=1" in the existing LDAP-UX profile configuration. Refer to “LDAP-UX Client Services B.05.02 Administrator Guide” (Section 2.4.6 Configuring LDAP-UX Client Services with SSL or TLS support) for further references.If ldapclientd still stops responding consuming 100% of CPU, starting ldapclientd in a loop with -z option may avoid the unresponsiveness, as shown below:# while : do/opt/ldapux/bin/ldapclientd -zdoneFor further investigation on the unresponsive, HPE support may require a core file of ldapclientd that can be obtained as follows./usr/bin/coreadm -p /var/opt/ldapux/core.%p -E /opt/ldapux/bin/ldapclientd -zThe core file generated will be named "core.<pid>" under /var/opt/ldapux.Document VersionRelease DateDetails2March 4, 2026Updated Description and Resolution.1December 22, 2025Original Document Release.
Operating Systems Affected:HP-UX 11.31 (IA)
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.