System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

diaglogd daemon failed to find entry for hardware path (255/0) in UUT status file

Charles Slivkoff
Respected Contributor

diaglogd daemon failed to find entry for hardware path (255/0) in UUT status file

During system boot, I've seen these messages from the hardware diags:

DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

I believe I've traced this to this message that I found in STM:

Diaglogd daemon failed to find entry for hardware path (255/0) in UUT status file (/var/stm/data/uut_status) for I/O error entry to be logged. Entry will be logged with NULL product information.

This path, 255/0, is used by the iSCSI driver. Does this imply that the diags do not know about iSCSI?

I've been diagnosing some hw issue with tape libraries, but I don't believe this is related. Can anyone offer any explanation of this message?

Thanks,

-Charles