Getting this error from time to time in the FglAM log files:
2011-07-15 10:44:10.002 WARN [Upstream Polling-0] com.quest.glue.core.comms.transport.http.Client - The server's SSL certificate indicates that its expected host name is different than the host name of the management server. This could indicate a potential man-in-the-middle attack or an incorrect SSL certificate on the server. If you have manually verified that the server being connected to is, in fact, correct then you can use the "ssl-cert-common-name" configuration property to override this check.
[...]
Is that something I need to be concerned about?
Transient connection failure or FMS certificate is expired.
This can be the result of a transient connection failure, not an invalid certificate or configuration failure. The error can ignored as long as FglAM does reconnect within a reasonable length of time.
Below the re-connection log file entry - please check the time stamp of the connection failure message and the re-connection message in the FglAm log. In this example it is around 20 seconds which is acceptable.
2011-07-15 10:44:29.142 INFO [Upstream Polling-0] com.quest.glue.core.comms.transport.http.Connection - Network connection to https://myFMSHost:8080 restored after 9 failed connection attempts.
1) Check fglam connection to FMS from FglAm cmd line:
cd $FglAM_HOME/bin
fglam --check-connection
2) If it fails to connect, this may be due to an expired FMS certificate. Reference KB48602
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center