We noted these type of messages sometimes in our FMS log. Should we be concerned?
Perhaps this is a FglAm condition on a client that the FMS did not expect a restart?
Change request FAM-2730 introduced this feature.
Addresses issue where the FglAm Adapter not knowing that the FglAM process had been restarted and thus did not attempt to (re)initialize the various states of the connecting FglAM. Allows the FglAM to notify the Adapter that it doesn't have a KeyExchange and have one initialized upon request.
ManagementServer_2011-09-30_174857_026.log:2011-10-17
22:40:59.744 VERBOSE [http-0.0.0.0-80-140] com.quest.glue.common.comms.HostStatus - Detected a rogue restart on downstream host [malibu/192.168.0.1] (Build: 55542-20110328-1620, ID: c72772fa-09f0-4027-978a-b52df34f1363). Resetting existing resource artifacts.
ManagementServer_2011-09-30_174857_026.log:2011-10-17
22:41:55.304 VERBOSE [http-0.0.0.0-80-172] com.quest.glue.common.comms.HostStatus - Detected a rogue restart on downstream host [malibu/192.168.0.2] (Build: 55542-20110328-1620, ID: c72772fa-09f0-4027-978a-b52df34f1363). Resetting existing resource artifacts.
SOLUTION:
The resolution is to identify the host which is reporting in with a different IP address and correct the fglam-config.xml file for the config:name and config:id for the incorrect FglAM. This reconfiguration can be accomplished via 'fglam --configure'.
Enh Req FGL-12868 Require alert for FglAm "rogue restart on downstream host"
https://support.quest.com/Search/SolutionDetail.aspx?id=SOL84085
