"scsi_dds" and "stm" processes on a server eating up cpu resources!

[TwoProc]

Hey all,
I've got a server with 70% of available cpu being spent on "sys" (from glance). A quick check in top shows a process called "scsi_dds" with tons of cpu time . I also see lots of time being given to a bunch of "stm" processes. They are about 35 of those. So, this looks like a case of runaway "cstm" or "stm" processes, and something else called scsi_dds.

Any help/suggestions appreciated.

[Sandman!]

scsi_dds points to DDS tape drives and/or autoloaders that may be attached to your server. Is stm hung trying to get status of DDS drives and/or autoloaders you have attached to your system?

~cheers

[Torsten. · Accepted solution]

If the diagnostic was started recently it consumes resources for a couple of minutes.

Did you receive messages about errors/failures /syslog/mail)?

Check if the stm version is current.

http://docs.hp.com/en/diag/stm/stm_upd.htm

[TwoProc]

Thanks Sandman,
I'm starting to believe that that cstm processes were trying to query the dds drive, and that it might be dead (I'll check this later today). I've not used that drive for quite a while, so it could have just given up the ghost, and the diagnostic went crazy trying to identify it. I just stopped the diagnosticd process, and manually killed off (-15) all of the cstms and stms and resources became normal once again. My guess is that it's time to check the patch level of that app (thx Torsten) and see if that dds is working.

Thanks all!

[TwoProc]

Tried to post points, but I am getting "system unavailable" for this, and another thread. I'll have to try again later for that. In meantime thanks Torsten and Sandman for your replies in both of my open threads.

[Andrew Merritt_2]

Hi,
scsi_dds is one of the STM tools, probably the Info tool (all the scsi_dds STM tools have the same name, but reside in different directories). What version of the OnlineDiags do you have? A problem like this was seen in very old (>4 years old) versions, but should not be seen with a current version. Run STM to check the version number, and compare with http://www.docs.hp.com/en/diag/stm/stm_upd.htm#table

Download the current version from http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

If you are also running HAO, check that you have a current version of that, and open a call with HP if both OnlineDiags and HAO are up-to-date and you still see the problem.

Andrew