Operating System - HP-UX
1839566 Members
2194 Online
110147 Solutions
New Discussion

HPUX B.11.11 U - ldapclientd

 
SOLVED
Go to solution
Stefano_36
Frequent Advisor

HPUX B.11.11 U - ldapclientd

Hi to all.

Problem is using the J4269AA product (LDAP-UX Integration) the ldapclientd process growths
unexpected the % of CPU used :

2 ? 927 root 152 20 18140K 3484K run 7349:27 100.35 100.18 ldapclientd

What can I check to avoid this problem ?
6 REPLIES 6
Jaime Bolanos Rojas.
Honored Contributor

Re: HPUX B.11.11 U - ldapclientd

Stefano,

If you are running LDAP-UX 3.20, see if you have the oportunity to upgrade to ldap-ux 4 integration.

Regards,

Jaime.
Work hard when the need comes out.
Steven E. Protter
Exalted Contributor

Re: HPUX B.11.11 U - ldapclientd

Shalom,

The process has a memory leak.

There are two options to fix it.

ldap client 3.3 or 4.0 both are available on http://software.hp.com

You will need to shut down the process prior to the upgrade.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Stefano_36
Frequent Advisor

Re: HPUX B.11.11 U - ldapclientd

Hi Jaime.
The LDAP-UX Client is already the Version B.04.00

thank you
Jaime Bolanos Rojas.
Honored Contributor

Re: HPUX B.11.11 U - ldapclientd

Stefano,

Looks like a loop in the ldapclientd, those loops could be caused by different reasons, this patch have been known to fix the loop: PHNE_34277.

If this patch does not work for you, the please open a case with HP so they can take a look at your specific case.

Regards,

Jaime.
Work hard when the need comes out.
Stefano_36
Frequent Advisor

Re: HPUX B.11.11 U - ldapclientd

Hi Jamie.

I found the path PHNE_34277 but reading the Description I dont find any information about my problem.
Why did you suggest to apply that patch ?

Thank
Jaime Bolanos Rojas.
Honored Contributor
Solution

Re: HPUX B.11.11 U - ldapclientd

Hi Stefano,

As I was stating above, that patch is known to fix the issue that you are having, I know you have a production environment and have not good reason to trust on what we post overhere and I completly understand, if you are not that sure about that patch, then you can always open a case with HP, most likely they will recommend that patch to you, but like I stated above, the problem might be for a different reason in your case.

This might be a really long resolution or a quick one if the patch works.

The good thing, you always have a big company like HP to support something like this :-).

Regards,

Jaime.
Work hard when the need comes out.