coda daemon memory consumption

[Francis Noël]

Hello forum people !

Have a few hosts running 11iv1 and OVPA through GlancePlusPak.

"ovpa version" ouput claims version C.04.50.00 of the ovpa bits are installed.

The situation is that the coda daemon, after running for a few days/weeks, registers in the glance process list as gobbling up 600+ MegaBytes of Resident memory.

This makes the coda daemon the most memory-hungry individual process on the host. Seems a bit much for metric collection and messaging.

Any idea if this is normal and how I might be able to reduce coda's footprint ? Memory is scarce at the moment.

Thanks !

[Steven E. Protter]

Shalom,

Independent confirmation seems called for:

http://www.hpux.ws/?p=8

Thats a memory leak detector.

SEP

[Francis Noël]

Thank you Steven

I will trace the daemon using the script you suggested and see if the Glance number agree.

When I bounce the daemon with an "ovpa restart" the resident memory used drops to 15 MegaBytes, which makes a lot more sense than 600+.

If I do observe the process requesting extra memory and never giving it back I'll search for some patches.

[Dennis Handly]

>never giving it back

The libc heap usually never gives memory back to the system. But it is available for recycling.

Of course this could be due to a memory leak.

[Francis Noël]

You are correct Dennis. Nevertheless 600+ MB for coda, up from ~15 just feels wrong.

The existence of PHSS_34301 leads me to believe that SEP was right in his assumption that this is a memory leak. The PHSS_34301 fix cannot be applied to a GlancePlus Pak install, as it is tailored for a straight OVPA install.

I have placed a call with HP software support in order to obtain the correct fix, if any.

I will post the outcome here when I get a response from the support team..

[Dennis Handly]

>Nevertheless 600+ MB for coda, up from ~15 just feels wrong.

Right.
(My comment was more toward your terminology. Leak is different than "never giving it back". Of course if you implied "to the heap" vs my assumption of "to the system", you were correct.)

[Francis Noël]

A patch was indeed the answer.
In order for OpenView patches to be applied over a GlancePlus Pak instance some OV common filesets had to be installed.

HP Support supplied an archive that comprised the required OV common filesets, required patches and scripts to automate the installation of each component.

If anyone encounters a similar situation with Glance Plus Pak C.4.5.0 I would recommend either to contact HP Support or upgrade to 4.6.

Word from HP support is that 4.7 will be out pretty soon and that 4.5 support will be discontinued at some point.

Hope this helps someone.

Thanks you everyone for your input.