KBI 311222 Issue Addressed: Daughter Engine Services Sharing SQL Server Database Might Skip Tasks Due To Frequent Recycling
Version
Argent Advanced Technology 3.1A-1504-A or earlier
Date
Tuesday, 2 June 2015
Summary
Argent AT Daughter Engine may recycle frequently when installed Argent AT product services share the same SQL Server database
If CMDB-X database has more than 3,000 Nodes, the recycling can take more than 5 minutes
As a result, Monitoring tasks can be skipped
For extreme cases, service may be caught in checkpoint error, recycle repeatedly and run no Monitoring Task at all
Service log shows following lines repeatedly:
The issue has been addressed in Argent AT 3.1A-1504-T1
Technical Background
The issue is caused by the inconsistence of CMDB-X in files of exported Master Control Information
Consider such a situation:
- Daughter Engine uses shared SQL Server database, and has Argent Guardian Ultra and Argent Sentry Ultra services installed
- There are 3,000 Windows/Unix/Linux servers and 300 URL objects in CMDB-X, monitored by Argent Guardian Ultra and Argent Sentry Ultra respectively
Say URL object X is monitored by Daughter Engine
Both Argent Guardian Ultra and Argent Sentry Ultra have exported Master Control Information, and exported files have been downed by Daughter Engine
- Customer removes URL object X and some other Windows servers in CMDB-X and exports Argent Guardian Ultra Master Control Information, but does not export Argent Sentry Ultra for some reason
- As a result, URL object X is removed at Daughter Engine
However, Argent Sentry Ultra at Daughter Engine still runs on the old Master Control Information, and continue monitoring URL object X though it has been unlicensed and removed at Mother Engine
Argent Sentry Ultra Daughter Engine adds URL object X back to CMDB-X
- Now CMDB-X does not match up the Argent Guardian Ultra Master Control Information
Argent Guardian Ultra at Daughter Engine recycles to import the CMDB-X database, and remove URL object X
- Argent Sentry Ultra will repeat Step 5
As a result, Step 5 and 6 are repeated constantly depending on how frequent the Monitoring Task of URL object X is executed
Resolution
Upgrade to Argent AT 3.1A-1504-T1 or later
For customer who cannot upgrade immediately, he should remember to export Master Control Information for all products when a CMDB-X Node is removed
As another resolution, he can turn ON Auto Export so that Argent AT Engine can do the export automatically
See KBI : https://help.argent.com/#KBI_310553.php