It is possible this is related to the recent leap-second event. Had you noticed it prior to the weekend? If this is the issue you can do this: # date -s "$(LC_ALL=C date)" Then if you restart the OMSA services it should be ok. Does that seem to improve things?
I have the latest OpenManage 6.5.0 from the Linux repository installed on an R510 server running CentOS 6.2. The dsm_om_connsvcd process is taking up 90% cpu, when no one is logged into server administrator.  After logging in, CPU usage goes to 330%. Has anyone else seen this behavior?
dsm_om_connsvcd uses 100% CPU