Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Plugin Agent starts a new task even when the previous task is still running. #43
Used the below Polling Plugin with a execute_frequency of 30sec
The script run as part of the plugin will establish a Grpc connection to the device and fetch Telemetry data.
The assumption is after 30sec , agent must not start the new task as there is no change in the configuration but we see its starting
As per the below logs we see that process 16135 is still running when the next process 16139 is started.
I have made the changes you have suggested(runner.py)
But I see issue when discovery agent is running
But the contender lock(a2cd4734-3667-4450-90ad-559713289f7c_plugin_ubuntu-14_23850) is from scheduler
Can you please chekc and let know if my analysis is correct.
Something doesn't seem right here - the Discovery Plugin Scheduler logs should not have entries for locks under the plugin_agent path. The lock related entries in Discovery Plugin Scheduler would look like:
Where the format of the identifier is
Would you mind sharing your logging.ini?
Attached logging.ini(Uploading with txt extension as .ini is not supported)
Discovery Plugin Scheduler
Discovery Plugin Agent