Receving Credential Alarms:
"Failure: Cannot establish connection to <hostname> : The connection was not established because either the key exchange or initial connection has timed out [Caused by: SocketTimeoutException <The kexTimeout (45000 ms) expired.> ]"
The following errors are seen in agent logs:
ECHO VERBOSE [Quartz[0]-7543] com.quest.remoteos.SystemMonitorImpl - The agent could not be configured to collect data for hostname, skipping collection
ECHO VERBOSE [Quartz[0]-7551] com.quest.glue.core.remoteconnection.ssh.SSHGanymedConnectionImpl - The connection, com.quest.glue.core.remoteconnection.ssh.SSHGanymedConnectionImpl@39d26f76, to hostname lost connectivity. Cause: Connection timed out
ECHO VERBOSE [Quartz[0]-7551] com.quest.remoteos.UnixAgentImpl - An SSH connection to hostname port 22 was not established
com.quest.glue.api.services.RemoteConnectionException: A connection could not be established to hostname:22
RESOLUTION 1:
Please test the SSH connectivity from the FglAM server to the monitored server using putty or another SSH application.
Once the SSH connection can be established using putty, clear the alarms in Foglight and problem should be resolved.
RESOLUTION 2:
Reconfigure the OS monitoring of the agents.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center