Do you see any of your playbook still in active state even after more than one hour?
Yes!
Does this mean playbook is till up and running?
No!.
Playbook execution time can not be more than the time limit mentioned in config file. The value of CELERYD_TASK_SOFT_TIME_LIMIT in file /opt/cyops-workflow/sealab/sealab/config.ini. Default
value of this is set to 10 min. That means if playbook exceeds this
time it will fail with Error: Time limit exceeded and this will set the
status of Playbook as Failed.
Then why it has active status still ?
In
some cases when playbook is up and executing and in the mean time we
restart celeryd service the process that was executing this will be
killed and playbook status in database remains in the same state i.e.
active. That is the reason we see status as active
To debug further Please check /var/log/cyops/cyops-workflow/celeryd.log .
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.