Hello, I have two similarly configured systems running a recent OpenSIPS 3.2 with may errors like this:
CRITICAL:core:io_watch_add: >>> fd_array idx 1 (fd=193) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil)) It seems you have hit a programming bug. Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues and ERROR:tls_openssl:openssl_tls_async_connect: failed to retrieve SO_ERROR [server=52.114.76.76:5061] (3) No such process ERROR:proto_tls:tls_async_write: failed to do pre-tls handshake! ERROR:tls_openssl:openssl_tls_accept: SSL_ERROR_SYSCALL err=Success(0) ERROR:tls_openssl:openssl_tls_accept: New TLS connection from 52.114.32.169:6912 failed to accept ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! ERROR:tls_openssl:openssl_tls_accept: SSL_ERROR_SYSCALL err=Success(0) ERROR:tls_openssl:openssl_tls_accept: New TLS connection from 52.114.132.46:3008 failed to accept ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! ERROR:tls_openssl:openssl_tls_accept: SSL_ERROR_SYSCALL err=Success(0) ERROR:tls_openssl:openssl_tls_accept: New TLS connection from 52.114.32.169:3072 failed to accept I'm wondering if this is truly a bug as the text suggests, or if I have a misconfiguration. I increased the number of file descriptors available to opensips in /etc/security/limits.conf on one of the systems about 10 minutes ago, and so far, no more errors. Normally I would have seen them by now. Both systems have low traffic, less than 1 cps. I don't have a lot of experience using OpenSIPS with TCP. It wouldn't surprise me if I've missed something. - Jeff
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users