Config push process Vs Appliance page config push force

Hello James,

The Config Push does 2 things:

• detect when a config table that should exist both on the CDB and each CU is not properly synchronized between the CDB and one or more CUs
• efficiently send that table to the CUs (and only those) that are out of sync. 

The Enterprise Database: Collector Config Push and Enterprise Database: Async Config Push (Force Config Push) perform the same function.

As these are 2 separate processes, technically the async process should run if the Enterprise Database: Collector Config Push process is disabled, however, it is imperative that Config Push is not disabled, as functionality of SL1 assumes that Config Push is operating normally and is a core process of SL1.

Antonio Andres

Principal Technical Support Engineer | ScienceLogic

Thanks Tony, 

Just to clarify, when i use the 'Force Config Push' option from the appliance page does that invoke the async_config_push.py process?

How can I check that the process is running or been run or the results?

When i click the force, it, i can see it does a DELETE FROM config_push.table_status WHERE collector_id='38'

But I can't see any processes start, and async_config_push.log empty. (with debug enabled)