Tracked configuration file empty file content - Support and Troubleshooting

Tracked configuration file empty file content Issue The horizontal discovery process can find configuration files that belong to certain applications and add those configuration files to the CMDB. In some cases, you may notice tracked configuration files where the file content is empty.

Each configuration file will have a hash value. If a tracked file exists for a host, the file name and hash values are sent down to the MID server when discovering the application. When the MID server collects an application tracked file it calculates a new hash. If the new hash and file name are the same to what we have on the instance this means the file has not changed and the content is emptied out, there would be no reason to send the file payload back to the instance as the content is the same.

In some cases there may be orphaned tracked configuration files, cmdb_ci_config_file_tracked, pointing to CIs that no longer exist. When this happens, a second tracked configuration file will be created for the same host and pointing to the new application CI.

Cause There are orphan configuration tracked files One with orphan CI and one with valid CI They both have same file name, which is used for identification cmdb_identifier.do?sys_id=e5d0703ac3022200adce9624a1d3ae76 They both have the same hash When discovery runs, it sends a list of tracked files for the host, at this point we don't exactly know what the application CI is (we only find out after identification) When the tracked file configuration logic runs, it "skips" as there is already a file with same name and hash Sends back an empty file content which gets matched to new application CI or created with new related CI In summary, orphaned configuration tracked files cause new configuration tracked files on same host with same hash to be created with empty file content.

Note: cmdb_ci_config_file_tracked table is set to cascade delete and therefore this should not happen often.

Resolution Find any configuration tracked files where the file content is empty Delete such files Find any configuration tracked files which are orphaned, for such the "Related CI" field will have a sys_id which points to no CI. Delete the orphaned configuration tracked files Run new discovery of the host Related Links Configuration File Tracking