cdm probe hangs on startup due to remote mount/disk missing
Article ID: 377721
Updated On:
Products
Issue/Introduction
The CDM probe will not start up.
It gets a PID but never gets a port.
The logs at level 5 show the following and then it just hangs forever:
cdm: InitDiskDefault - section /disk/fixed_default
cdm: ResetDefaultStruct
cdm: Value gDiskMissingFlag 1
cdm: Value gInNodeErrorFlag 1
cdm: Value gDiskErrorFlag 1
cdm: InitDisks - tag existing profiles
Environment
cdm probe 7.21 and lower (tested to at least 6.84)
Cause
The probe may fail to start and hang indefinitely when there is an inaccessible or missing remote disk configured for monitoring. There is a defect in the probe where the command to obtain the disk details does not properly time out when the remote system is not responsive.
Resolution
This will be resolved in the next release of the CDM probe after 7.21.
Meanwhile, as a workaround - if applicable, you may need to investigate to find out why the mounted disk is not accessible - for example, the remote server which hosts the mounted disk may be down/not responding.
If this is expected (for example, the server is under maintenance or has been decommissioned), you will need to edit the cdm.cfg file and remove the reference to the remote disk.
You can locate the appropriate entry by looking for the following string in the cdm.cfg file, which will appear in each entry for a remote/mounted monitored filesystem:
file_system_type = nfs
An example entry might look like the following:
<#example#path#to#filesystem>
active = yes
description = File system /example/path/to/filesystem
disk = <ip_address>:/mnt/example
file_system_type = nfs
....
You can either remove the entire section that references the filesystem or simply change "active" to "no" for the entry that corresponds to the missing/down/inaccessible filesystem and restart the cdm probe.
Once the probe starts up, you may delete the entry/remove the filesystem from the configuration using the GUI.
Feedback
