Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On a couple of occassions jobs on my Redhat Linux server hang up due to IBM Director's "cimserver" processing using 100% of the CPU.

Seen on,

Redhat 2.6.18-8.el5PAE #1 SMP Redhat 2.6.9-67.ELsmp #1 SMP

This Technote (in Japanese!!) seems to deal with a similar problem:

Does anyone know what triggers this?

share|improve this question
What version of Director? What release/patchlevel of RHE? – MikeyB Jun 1 '09 at 1:40
I'm not the administrator of Director on this sytem. Is there a simple way to query it from the command line to get this information? Redhat release numbers were given above. – Stuart Woodward Jun 1 '09 at 4:00
up vote 1 down vote accepted

Assuming this is a binary only program, the best way to work out what it's doing is using strace. The first thing to do is to find out what it's doing now:

strace -f -o /tmp/cimserver.log -p $process_id

You can then look in /tmp/cimserver.log to see what system calls it's doing. You may find that the problem happened before now, in which case you'll need to run the process under strace from the start.

strace -f -o /tmp/cimserver.log /usr/sbin/cimserver $args

Beware this will slow the process down a reasonable amount. You can reduce the logging to particular system calls by using the -e option. Check the man page for more info.

Hopefully this will give you some pointer to the problem. Of course it could just be a bug in the software :)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.