NV Version: All
OS Version: Linux, Windows
Application version: N/A
Plugin version: N/A
Description: Explanation as to why NetVault sometimes cannot be restarted without rebooting
Symptoms: The NetVault service has been stopped (either on purpose or through a crash). When trying to restart the service, it just goes into a stopped state again.
Sometimes, this can be down to a corrupted database.
However, in some cases (and trace on process, communications and network manager will show this) there is still a NetVault process lingering in memory from the previous run. This is most likely nvdevmgr - it is the only NetVault process that is loaded into kernel instead of user space due to the requirement to communicate on the SCSI bus, and it's difficult to shut these processes down in a controlled manner when Windows keeps hold of them. Eventually, the OS should clear them up once the service is stopped - but it might take a while. If waiting is not acceptable or doesn't lead to the processes being removed from memory, rebooting is an option.