How to sycnhronize the catalog
...
If after completing the above steps the catalog status has not changed then the receiving of the sync message should be validated.
The appliance by default writes all incoming and outgoing messages to the directory "/opt/iqas/server4.5/tmp/messages".
Look for a message called called i_catalog-bkgnd-sync-******* -D275.msg .
If it is not present then try the synchronization steps again to rule out the possibility of an (unlikey) lost message.
If it is present then the logs should be consulted, look for the following content:
PIIIIIIIICCCCCCCCC HERE
If the logging is present without exception, validate the catalogVersion content of the heartbeat message:
| Code Block |
|---|
~orgOid=<tenant>
~masterAppliance=<tenant>:Appliance:<masterApplianceName>
~serviceName=notifier
{
"catalogVersion": "[
{\"ownerOrgId\":\"SYS:SolProvider:sys\", \"versionByEntity\":15, \"version\":6158, \"entity\":\"ScanExtension\"},
{\"ownerOrgId\":\"SYS:SolProvider:sys\", \"versionByEntity\":414, \"version\":6158, \"entity\":\"PIEntry\"},
{\"ownerOrgId\":\"SYS:SolProvider:sys\", \"versionByEntity\":149, \"version\":6158, \"entity\":\"Manufacturer\"},
{\"ownerOrgId\":\"SYS:SolProvider:sys\", \"versionByEntity\":265, \"version\":6158, \"entity\":\"Signature\"},
{\"ownerOrgId\":\"SYS:SolProvider:sys\", \"versionByEntity\":15, \"version\":6158, \"entity\":\"OSFamilyEntry\"}
]",
"lastStatusDate": 1554426549135,
"buildVersion": "4.5.808",
"applianceName": "<tenant>:Appliance:<applianceName>",
"orgOid": <tenant>,
"masterAppliance": "<tenant>:Appliance:<masterApplianceName>",
"timeZone": "Europe/Dublin",
"serverId": "<serverId>",
"registrationKey": "<registrationKey>",
"command": "applianceAlive"
} |
If the heartbeat message content has not been updated there is a java issue which needs escalation.
If the heartbeat message content has been updated but the Cloud UI status has not changed there is a communication/cloud side issue which needs escalation.