CDM probe hang due to unresponsive filesystems in AIX
Article ID: 443435
Updated On:
Products
Issue/Introduction
The probe cdm port on a server (Robot) running AIX cannot be activated even though the server is running. It does not get a port and it is not generating any log.
The issue appears to be caused by the cdm probe hanging while attempting to query filesystem metadata from storage drives that are unresponsive at the operating system level.
Environment
- DX UIM 23.4.*
- cdm 7.* / 8.*
Cause
The cdm probe executes system calls (such as 'df -g' on AIX) to scan filesystems during startup. If a mounted filesystem or network drive is unresponsive or hanging at the OS level, the probe process may hang indefinitely waiting for an I/O response, preventing it from opening its command port.
Resolution
To resolve the port activation hang, identify and exclude the unresponsive filesystems or configure the probe to bypass problematic network mounts.
Identify Unresponsive Mounts
- Log in to the affected AIX server terminal.
- Run the command df -g.
- If the command hangs and does not return to the prompt, this confirms the operating system is stuck waiting for a response from a storage device or network file system.
- Work with system administrators to resolve the underlying hardware or connectivity issue for those specific disks.
Exclude Problematic Filesystems
- In the cdm configuration (IM or AC), navigate to the Setup tab.
- Check the box for Filter ignored disk from List.
- Use the Ignore Filesystems field to exclude unresponsive drives using a regular expression. For example, to only monitor local JFS2 filesystems and exclude others: filesystem_type_filter =
/^(jfs|jfs2)$/ - Alternatively, to ignore everything while troubleshooting:
* - Restart the cdm probe.
Additional Information
Feedback
