ExpertHello James,
Affirmative, clicking the Force Config Push button runs the async_config_push.py process.
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
ModeratorHello James,
The Enterprise Database: Async Config Push runs on the primary CDB so that is where the logs should be.
The Enterprise Database: Collector Config Push should be running every minute so you shouldn't have to be running the Enterprise Database: Async Config Push unless instructed by Support to address an issue. What are you trying to accomplish?
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
ExpertWhen large ppks are deployed, config push will try to push to all collectors, causing connectivity disruptions to the collectors, and so i can take hours even days in some cases to push updates.
To try mitigate that i'm thinking to disable config push and use the async force config push on small number of collectors at a time.
ModeratorHello James,
Do you have a support incident open to investigate these issues with Config Push? It is not expected for Config Push to run longer than 20 minutes or cause collectors to disrupt connectivity, even on larger stacks, so there is likely an issue happening that is causing this behavior that needs to be investigated.
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
ExpertLooks like an connectivity issue between the DC and CDB ,usually it should not take that longer
