Remote log file monitor troubleshooting

$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('

'); $("#ic-homepage__feed-tips").wrapInner('

'); });

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Log File Agent User's Guide > Troubleshooting > Problems and workarounds IBM Tivoli Monitoring, Version 6.3

Remote log file monitor troubleshooting

Problems can occur with agent communications to the remote system for remote log file monitoring.

Remote log file monitor problems and solutions

Problem Solution
No events or data is read from the remote log file. Check the Log File Status File Status. If it shows OK, then the file is being monitored.
Log file Status does not show OK File Status.
Check the File Status that relate to remote files:

PASSWORD EXPIRED

expired password.

PUBLIC KEY UNRECOGNIZED

A certificate cannot be read (bad passphrase or bad file).

PUBLIC KEY UNVERIFIED

A certificate cannot be verified.

NO SUPPORTED DESCR

A remote system does not support any of the authentication methods that are described in Supported SSH capabilities and features.

SOCKET_TIMEOUT

A communications time out. Possibly from a firewall or a broken connection.

KEY FILE ACCESS ERROR

A public or private key file cannot be found on the local system.

HOSTNAME UNRESOLVED

The domain name server (DNS) cannot resolve the remote host name.

FAMILY UNSUPPORTED

The IP address of the host name that is returned from DNS is not an IP supported family (IPv4 versus IPv6).

Log File Status does not show one of the values in the previous two troubleshooting entries for File Status.
From the system that is running the Log File agent, use SSH, SFTP, or SCP with the remote parameters (userid, password, certification, filename) and verify that the file can be read.
None of the previous troubleshooting entries help resolve the issue.
Turn on the following trace: ERROR (UNIT:KUMPLIBSSH STATE). This setting produces a trace of all libssh2 communication between the Log File agent and the remote system. Look up any nonzero return codes for the APIs. For more information about using trace logs, see Trace logging.

Parent topic:
Problems and workarounds

+
Search Tips | Advanced Search

Problem	Solution
No events or data is read from the remote log file.	Check the Log File Status File Status. If it shows OK, then the file is being monitored.
Log file Status does not show OK File Status.	Check the File Status that relate to remote files: PASSWORD EXPIRED expired password. PUBLIC KEY UNRECOGNIZED A certificate cannot be read (bad passphrase or bad file). PUBLIC KEY UNVERIFIED A certificate cannot be verified. NO SUPPORTED DESCR A remote system does not support any of the authentication methods that are described in Supported SSH capabilities and features. SOCKET_TIMEOUT A communications time out. Possibly from a firewall or a broken connection. KEY FILE ACCESS ERROR A public or private key file cannot be found on the local system. HOSTNAME UNRESOLVED The domain name server (DNS) cannot resolve the remote host name. FAMILY UNSUPPORTED The IP address of the host name that is returned from DNS is not an IP supported family (IPv4 versus IPv6).
Log File Status does not show one of the values in the previous two troubleshooting entries for File Status.	From the system that is running the Log File agent, use SSH, SFTP, or SCP with the remote parameters `(userid, password, certification, filename)` and verify that the file can be read.
None of the previous troubleshooting entries help resolve the issue.	Turn on the following trace: `ERROR (UNIT:KUMPLIBSSH STATE)`. This setting produces a trace of all libssh2 communication between the Log File agent and the remote system. Look up any nonzero return codes for the APIs. For more information about using trace logs, see Trace logging.