I am using OpenManage 5.5.0 on a Dell PowerEdge 2900 server running Windows Server 2003 SP2.
When I start Server Administrator and click on "Logs" and then "Command", the dsm_om_connsvc32.exe process uses up 100% of one of the two CPUs and the Server Adminstrator hangs.
I must restart the DSM SA Connection Service in order to restore operation.
Thanks for posting! There are two likely causes, either something runs into an infinite loop in that process, or it is processing a user request that can't be answered. You might want to try running WireShark or Ethereel to see if there is any external activity. If not, make sure everything is up to date and repair or reinstall OMSA.
Your suggestions will not work as this is a brand new server with the shipped OMSA installed (version in my original post). There are no ther users or processes except my self involved.
My intention was to re-inforce the thread opener's problem:
"When I start Server Administrator and click on "Logs" and then "Command", the dsm_om_connsvc32.exe process uses up 100% of one of the two CPUs and the Server Adminstrator hangs.
I must restart the DSM SA Connection Service in order to restore operation."
My experience is exactly the same with a newer version of OMSA.
well, it appears that I already had this loaded, but it was Om 6.2. I should note that Om 6.1 didnt have full support for 2008 R2. As I was saying, my OM 6.2 installation is not seeing a problem with the dsm_om_connsvc32.exe after clicking Logs, then Command. I can dngrade the OM, but wouldnt be until tomorrow.
messier11
2 Posts
5158
0
Posted March 30th, 2009 16:00
Has anyone else had the same issue of dsm_om_connsvc32.exe consuming excessive CPU?
Can someone try to reproduce by clicking "Logs" and then "Command" from within Server Adminstrator?