No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Not reboot watchdog service after diskguard configuration information changed leading diskguard service abort

Publication Date:  2012-09-20 Views:  227 Downloads:  0

Issue Description

Diskguard protect policy is configured, the disk synchronize set to 24:00. But disk did not synchronize the next day and diskguard service abort. 

Alarm Information


Handling Process

Kill diskguard process (open task manger, click right button on the diskguard and choose close process), reboot diskguard service (click right button on diskguard service and select startup). Reboot watchdog service.

Root Cause

Local ip is changed when configure diskguard while watchdog service does not reboot, making watchdog constantly searching previous ip service and reboot every 3 minutes if no ip service found. There is diskguard service startup information generated in windows log every 3 minutes.


When configure diskguard policy, if diskguard parameter is changed, watchdog service should reboot.