How to set a longer timeout for the Control Managers alive Checking

[nicolas.chaix]

Dear community,

I have programmed a control manager script which takes a long time to make its cycle (more than 30 s for its 1st cycle) and this is normal because it scruts a very long dyn_string.
This causes a CrashAction (control manager in status '3') after 30s due to an heart beat loss, and, once the script cycle over, come back to a normal status.
Is there a possibility to change this 30s time to a longer one? Or is there a way to give to the system (pmon I suppose) an heartbeat signal to avoid it?

Thanks for your help

Kind regards,

Nico

[mkerk]

Hello,
with the config aliveSeconds in the pmon-section it´s possible to change the default value of the pmon alive counter. e.g.:

[pmon]
aliveSeconds = 60

BR,
Mousser

[nicolas.chaix]

Hello Mousser, thanks a lot for this tip.

Best regards

[gschijndel]

Or is there a way to give to the system (pmon I suppose) an heartbeat signal to avoid it?

You could try a 'delay(0);' to force a control thread switch before a long function call and might give the manager some time to signal a heartbeat.

[leoknipp]

Using a delay(); in the CTRL script will not force a thread switch.
When a function is executed which takes long time, e.g. sorting a huge dyn array, it cannot be interrupted and it possibly leads to the information from the process monitor that the manager is blocking.

Best Regards
Leopold Knipp
Senior Support Specialist