Hi Daniel,

We build ver. 5.3.1 from sources. So, probably we should enable this flag in our build script. How to do that?

BTW. Also, we need some rpc command that closes all WS connections. I'm suggesting something like this:

void ws_rpc_close_all(rpc_t *rpc, void *ctx)
{
int hash, ret;
ws_connection_t *wsc;

WSCONN_LOCK;
wsc = wsconn_used_list->head;
while(wsc) {
ret = close_connection(&wsc, LOCAL_CLOSE, 1000, str_status_normal_closure);
}
WSCONN_UNLOCK;
}
 
but I think the code above is not so quite safety and may causes deadlock. How to close the connections properly?


Thanks,
Andrey



вт, 21 янв. 2020 г. в 15:37, Daniel-Constantin Mierla <miconda@gmail.com>:

Hello,

if you installed from deb packages provided via deb.kamailio.org, upgrade to latest 5.3.x (now 5.3.2), the fix to use process shared mutex in libssl 1.1 was not enabled before due to a packaging mismatching make condition.

Cheers,
Daniel

On 20.01.20 12:07, Andrey Deykunov wrote:
Hi guys,

Got the issue on 5.3.1 with openssl1.1, debian9.
After 3 working days of tests (about ~30-50 WSS clients), suddenly we've got
a lot of connections stucked in CLOSE_WAIT state. Kamailio called
sig_alarm_abort() when we try to reboot.

Thanks,
Andrey  

_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com