Frequent restarts of "HP Systems Insight Manager"

[IT QA]

We are running HP SIM 5.1 SP1

We are having to restart the "HP Systems Insight Manager" on a regular basis because we cannot connect via HTTPS.

Are there any general reasons as to why this happens or any useful documents that could point us in the right direction
Regards

[David Claypool]

What is the hardware and OS configuration of the host running HP SIM?

[IT QA]

Windows 2003 SP2 and HP Blade

[IT QA]

Anyone out there have any ideas as to why the HP Insight service Manager needs to be restarted frequently

[rj01]

I am having a similar issue (and posted it previously), but with 5.2. I have to restart the service to get into the web page about every 2 days at this point. If I don't, eventually SIM stops working.

The only error I get is "
Audit Log queue size exceeded, audit logging paused, verify mxdtf is running,"
however the log is well below the default maximum size according to HPs documentation.

If anyone has any ideas, it would be greatly appreciated.

[Jamie Coleman]

This same problem has started occuring for me also in the last month. Any ideas guys?

David - SIM5.2 with SP1 (C.05.02.01.00), Win2K3 R2 Std x32, HP BL460c G1.

Cheers,

[Jamie Coleman]

A bit more info...

It seems I am generating the default max mx log filesize (20MB) every few days which coincides with my restarts (>1000 devices in SIM). My last rollover log file time stamp is around the same time users reported the HPSIM site stopped responding. Seems there is a problem with the rollover of the mx log file. I could create a log.properties file and specify a bigger log file size, but this would only postpone the reboot not fix the problem.

[corinne haesaerts]

Have you logged this as a problem with HP ?
Is support looking into it ?

[Jamie Coleman]

Yes and Yes.

[mark q]

same thing with me, any word on a fix from hp?

[Jamie Coleman]

Apologies for not updating this thread earlier.

A.05.05 Service Essentials Remote Support Pack requires that it is installed on the system drive (C:).

Not sure if this was a requirement in previous versions of the RSP software but it seems this issue hit us as soon as that version was installed automatically by Remote Support Software Manager App.

The eventual recommendation from a few weeks of sending logs back a forth was to reinstall the Server Essentials Remote Support Pack to the system drive (C:) as per the documentation.

We ended up taking this opportunity to do a full system rebuild with a new database. Problem has not reoccurred.

[Ragarc]

I have ICE 3.0 installed in drive F: using the integrated installer and I am having this problem. RSP got installed on the F: drive too. Is the solution still to move RSP to the C: drive?