-
Title
Linux Agent not collecting and host not listed in the Infrastructure or Hosts Dashboard. ERROR: The unique system ID for the current system could not be determined. -
Description
In Agent Properties, the hostname override field is not set
SystemId = Unset; see screenshot
-
Cause
From the last agent logs(2015-07-30 15:57), UnixAgent Monitor@issuedhost.foglight.com should collected data successful.Also could find the Host info from info.txt:---Common Topology Values [Host.name=issuedhostHost.primaryIPAddress=#.#.#.#Host.systemId=null]----And the current system could not be determined:2015-07-30 15:57:42.075 DEBUG [Quartz[0]-0] com.quest.glue.core.services.TopologyDataSubmitter3 - The unique system ID for the current system could not be determined. -
Resolution
Following the steps below:
- Edit Agent Properties, set "Host name override" to your desired hostname; in this case was "issuedhost.foglight.com" , and select "Collect System ID" to false .
- Edit fglam config file $FGLAM_HOME\state\default\config\client.config and set following: system.id.enabled = false;
- Restart FglAM and check the dashboard again.
This is something related to the Operating System. Sometimes when a virtual machine is cloned it keeps the same system id as an existing one or do not generate this system Id causing this type of problems.
Reference: KB 119341
Make sure that each cloned VMWare is having a unique bios.uuid. The bios.uuid can be found in the *.vmx file.
The VMWare knowledge base provides the steps to change the bios.uuid in article 1002403. If further help is needed, please contact the VMWare support team.
Related Articles:
WindowsAgent or UnixAgent Infrastructure Agent never shows up in Agents on All Hosts dashboard
Editing a virtual machine with a duplicate UUID.bios (1002403) - Edit Agent Properties, set "Host name override" to your desired hostname; in this case was "issuedhost.foglight.com" , and select "Collect System ID" to false .