High CPU Utilization on Insight Manager 7

[Scott Perrin]

Java.exe causing CPU utilization to stay at 50%

[Scott_192]

I had the same problem. The error started occurring on 2/17. I was assumming it was a Microsoft patch or Compaq 7.2a agaents that was the factor. I backed several patches off and changed Java version, it still failed. The memory leak would take the server down in about an 1 hour. I am still not sure what the cause was, but, I reloaded the server from a backup done on(2/13), and did not apply any patches. After that, the restored server was pacthed with MS patches and Compaq 7.1 agents. All is OK. Did you apply the 7.2a agents????? If so, you might want to check them. I have them installed on a test server and they are fine.

[Bill Bohlen]

We are starting to experience this as well, on a server that's been running Insight Manager just fine for three years now.
The JAVA.EXE process is taking up a ton of CPU time and memory when it hadn't before.
Our servers all have pretty old insight agents....all the way back to Compaq version 5.40. Until recently, the latest version we SmartStarted with was 6.40. We just got several new servers built, but I checked and they were built with the 7.10 CD. We started getting this problem on 3/5. If I stop and start the Insight Manager 7 service it goes away for awhile then reappears. Let me know if you find anything else out,

Bill

[Christopher Miller_4]

have you solved this problem yet \ same thing here

[Scott Perrin]

We haven't been able to solve the problem yet but we have also noticed the memory leak. The server runs out of memory after an hour. This could be patch related, we follow the MS patch schedule and it seems the problem started after we applied the January security patches.

[Bill Bohlen]

Well right now I'm trying to see if I can run the Insight Manager service in some sort of debug mode. I noticed that the service executable C:\WINNT\System32\InsightXESvc.exe can be run from the command line with a -debug option. However, this does not produce any noticeable debug output. I wonder if there are additional debug parameters that can be added?
I'm actually writing up a plan to migrate to HP Systems Insight Manager now, since I don't think we are going to get an answer for a retired product like IM7.

[JP_MandG_Please_Remove_]

I am also getting this problem. Started happening after the weekend of the 19th Feb. For the life of me I don't know what is causing this to happen. I have also noticed that some events from servers (such as Hard drive failures) are not being reported in CIM 7 since that time also.

I have started removing security patches that were applied to the server but I have yet to find one that may have caused the issue.

Has anyone from HP heard of this and have a solution for us ?

[E van Brecht]

Same here. It seems problems started after the following MS updates:
867282
891781
885834
885250
888113
890047
873333
886903
I'm trying to narrowing down the update(s) that caused the problem.

[JP_MandG_Please_Remove_]

I am doing the same .... I think I may have stabalised it on 890047, but I am not too sure as it takes a couple of days till it goes mad again ....

Java.exe is still getting larger, but a lot less slowly than previously.

Evan, could you post up here when you find the one that you think may be the issue.

Thanks.

[E van Brecht]

hehe Jason, I had to look twice before I realized you meant me "Evan". The "van" part is actually part of my silly dutch surname :-p
I deinstalled all patches from the server resulting in a blue screen at boot. I reinstalled 2003 in the same folder to get the server up and running. Even though all patches are still deinstalled (and lots more), the problem still occurs. Not much help I know. Within minutes the java.exe takes 500MB and more mem.
Time for HP/MS to come up with a sollution if you ask me.
Grt'z Ed

[JP_MandG_Please_Remove_]

hehehe ... sorry Ed :-)

I agree with you, probably HP/MS should step in here with a little bit of advice, as I am sure this has not just effect the small lot of us in this thread alone.

I will try keep you guys up to date with what I have found otherwise.

Cheers

Jason

[Bill Bohlen]

Well I took the leap and upgraded to HP Systems Insight Manager 4.2.
MUCH BETTER.
No longer do I have the CPU issues, and also I don't have to have the 1.3.1_09 Java environment to run it. HPSIM will run with any JRE higher than 1.4.1.

[JP_MandG_Please_Remove_]

Hi Bill,

I too have a SIM 4.2 server here but won't put it live as the issues I have a severe memory leak in the mxdomainmgr.exe process as well as the events from my old 7.2 server do not get migrated across properly to 4.2 and also the event handling is quite un-user friendly to amend or add more events in....

I won't get into this on this thread... there is another thread somewhere on the ITRC that has the issues with that release.

Cheers

Jason

[E van Brecht]

Status update:
I had to reinstall Win2k3 in the same windows folder to get the system up and running again. It showed a blue screen after the reboot when I deinstalled the eight MS patches mentioned earlier in this thread.
Since this still did not fix anything I reinstalled the patches without result again. Now I installed SP1 and it seems a lot more stable. It's to early to say the problem is fixed but memory and cpu are at acceptable levels.
Only thing that seems a bit odd is the number of threads and handles. resp around 170/1090. I'll let you know if any more news comes up.
Grt'z

[JP_MandG_Please_Remove_]

Ed,

I am using Windows 2000 on SP3. If this still happens I think I might rebuild the server with 2000 and SP4. But at the moment the server seems to have stabalised and has been up for the longest time it has been since all this happened. The patch I uninstalled I mentioned in a couple of posts back ...

[E van Brecht]

Last update from my side: I can say with certain certainty that the problem is solved. The Java.exe is behaving like an angel and IM works like a charm. One of the stack off changes in SP1 must have done the trick.
GL, Ed

[Christopher Miller_4]

Jason Pope,

What was your solution to the problem. I read that the problem was solved on W2K3 with SP1. But like you i am running only W2K SP3. Did you install SP4? or was the patch removal the solution?

[JP_MandG_Please_Remove_]

Christopher,

After removing security patch 890047. I have found my system to be more stable. Though java.exe does grow a little it does not grow quickly or take over processing power. I think it may have fixed it but will have to keep my eye on it.

Try it on your system and see what you get. I did remove other patches before it, and will probably re-add them to see if it was a cumulative solution or just a one off.

Cheers

Jason

[Gotink]

Same problem over here.
I think we solved it bij deïnstalling the HP System Management Homepage service.
You also have to downgrade version control (agent 2.1 en repository 2.1) because they depend on this servi

[Gotink]

Same problem over here.
I think we solved it bij deïnstalling the HP System Management Homepage service.
You also have to downgrade version control (agent 2.1 en repository 2.1) because they depend on this servi

[JP_MandG_Please_Remove_]

Albert,

But Compaq Insight Manager 7 does not contain a System Management Homepage. System Management Hompages are in HP SIM 4.x. Also the version control agent is already 2.0 not 2.1. Default install of Compaq Insight Manager 7 with 6.4 agents. So this is not really a solution.

[Gotink]

Supportpack 7.20 contains this new (homepage) service and version control 2.1

[JP_MandG_Please_Remove_]

Albert I agree with that, but in this situation we, and I expect most people are running Insight Manager 7 with 6.4.

I don't have the 7.2 agents on the server and I am getting this problem. So in light of this this is not a solution.

It happened to a lot of people at the same time which has been traced back to a security update that micosoft probably released and was installed.

[Gotink]

Ok, but we use Windows 2000 sp4 without patch 890047

[JP_MandG_Please_Remove_]

Albert,

I am doing the same. I have removed that patch, but just recently it has done it again. So I am back at removing other patches.