Veritas Operation Manager process MH_DRIVER.PL is constantly respawned and consumes CPU resources

Article:TECH166401  |  Created: 2011-08-03  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH166401
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Environment

Subject

Issue



Veritas Operations Manager (VOM) process MH_DRIVER.PL is constantly respawned and consumes CPU resources.


Error



mhrun.log:

Tue May 31 08:58:11 2011 [error] mh_driver: V-0000-0000 /opt/VRTSsfmh/bin/mh_driver.pl is already running for VCS.
 Arguments: --family VCS --hidden --context optimize=off
Tue May 31 08:58:18 2011 [error] mh_driver: V-0000-0000 A recan is already running. Terminating this run
 Arguments: --family VCS --hidden --context optimize=off
Tue May 31 08:58:19 2011 [error] mh_driver: V-0000-0000 A recan is already running. Terminating this run
 Arguments: --family VCS --hidden --context optimize=off
 

<... message repeats ...>
 


Environment



VOM VRTSsfmh 4.0.1097


Cause



Defect


Solution



Work Around:

Stop Near-Real-Time discovery (NRT) for VCS.

/opt/VRTSsfmh/adm/vxvmdiscovery-ctrl.sh stop

This will prevent the problem your are seeing but still allow for a 60 minute discovery cycle.

When the permanent fix is implemented you should restart NRT discovery without seeing the mh_driver.pl issue.

Permanent fix:

HotFix vom-HF040010970-07

 

Patches available at:SORT (http://sort.symantec.com)

 

https://sort.symantec.com/patch/detail/5252/0/cGF0Y2gvcGF0Y2hfbGlzdC8y

 




Article URL http://www.symantec.com/docs/TECH166401


Terms of use for this information are found in Legal Notices