[OpenSIPS-Users] exec timeout warnings

[Liviu Chircu]

Hi John,

Thanks for the report! It seems the "time_to_kill" feature is somewhat 
broken, in that it's not invalidating the scheduled expirations at all 
in case the job actually completes within time. So, when the job 
"expires", the code will actually fire off a SIGTERM to the former pid, 
which could have been (in theory) allocated to a completely new process!

However, thanks to monotonically increasing pids and the fact they grow 
rather slowly in the majority of cases, the kill itself, as well as the 
warning should be harmless. I'll take care of fixing it asap, though - 
that behavior is not desirable!

Best regards,

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 12.03.2018 20:28, John Quick wrote:
> Hi,
>
> I'm attempting to upgrade some OpenSIPS Proxies from v2.1 to v2.3.2.
> The script uses the exec function to execute some external commands.
> Using the new v2.3.2, I now see an "exec timeout" message (INFO) for every
> exec call. Here is an example:
> INFO:exec:timer_routine: exec timeout, pid 29175 -> sending SIGTERM
>
> This is new. It was not happening in v2.1. It doesn't seem to make sense in
> so far as the exec function has returned a result immediately to the script.
> Also, the process started by the exec command would terminate as soon as it
> has returned a value.
> The timeout warning is written to the logs about 3 seconds after the exec
> function was called, matching the setting for timeout in the exec module
> modparam section.
>
> John Quick
> Smartvox Limited
> Web: www.smartvox.co.uk
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users