Re: [OpenSIPS-Users] TCP-related errors
Just as a quick update here, the whole troubleshooting is undergoing in the GH ticket, as Ben mentioned. And so far, a it seems to be TLS specific, not TPC, and even more, to be related to the TLS async writing. For the moment it's WIP. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS eBootcamp 2021 https://opensips.org/training/OpenSIPS_eBootcamp_2021/ On 1/12/22 2:59 AM, Ben Newlin wrote: We are just migrating to OpenSIPS 3.2 and I also have seen these errors, though I saw them under significant load. I opened a Github issue for it here: https://github.com/OpenSIPS/opensips/issues/2724 <https://github.com/OpenSIPS/opensips/issues/2724> Ben Newlin *From: *Users on behalf of Jeff Pyle *Date: *Tuesday, January 11, 2022 at 7:25 PM *To: *OpenSIPS users mailling list *Subject: *[OpenSIPS-Users] TCP-related errors 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=2000,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 <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 <http://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 <http://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 <http://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 <http://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 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] TCP-related errors
We are just migrating to OpenSIPS 3.2 and I also have seen these errors, though I saw them under significant load. I opened a Github issue for it here: https://github.com/OpenSIPS/opensips/issues/2724 Ben Newlin From: Users on behalf of Jeff Pyle Date: Tuesday, January 11, 2022 at 7:25 PM To: OpenSIPS users mailling list Subject: [OpenSIPS-Users] TCP-related errors 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=2000,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<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<http://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<http://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<http://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<http://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
[OpenSIPS-Users] TCP-related errors
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=2000,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
