We found most of the time, it follows a global (per process) buff and is followed by a per connection buff and then the message is read.
Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_read_req: *Using the global ( per process ) buff * Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_update_fd: New fd is 118 Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tcp_handle_req: *We didn't manage to read a full request* Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_read_req: tls_read_req end Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_read_req: *Using the per connection buff* Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_update_fd: New fd is 118 Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:_tls_read: *683 bytes read* The one I mentioned in the previous email was not followed by a per connection buff and it seems the connection was dead. Oct 19 13:35:05 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_read_req: *Using the global ( per process ) buff * Oct 19 13:35:05 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_update_fd: New fd is 118 Oct 19 13:35:05 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tcp_handle_req: *We didn't manage to read a full request* Oct 19 13:35:05 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_read_req: tls_read_req end Oct 19 13:35:07 sipserver /usr/sbin/opensips[18622]: DBG:tm:timer_routine: timer routine:2,tl=0x7f0fc18a3630 next=(nil), timeout=428446 Oct 19 13:35:07 sipserver /usr/sbin/opensips[18622]: DBG:tm:wait_handler: removing 0x7f0fc18a35b0 from table Oct 19 13:35:07 sipserver /usr/sbin/opensips[18622]: DBG:tm:delete_cell: delete transaction 0x7f0fc18a35b0 Oct 19 13:35:07 sipserver /usr/sbin/opensips[18622]: DBG:tm:wait_handler: done jacky z <[email protected]> wrote: > Thanks! We found an end point sent an INVITE, but the server did not > receive. The time of this message in the opensips log matched the INVITE. > Not sure whether the INVITE message failed to be read for whatever reason. > Then we checked the server and found a lot of such messages. The server is > a still a test server and we don't expect there are a lot random connection > attempts. > > Giovanni Maruzzelli <[email protected]> wrote: > >> On Wed, Oct 20, 2021 at 11:00 AM jacky z <[email protected]> wrote: >> >>> >>> Recently checked the log and found a lot of items. >>> >>> DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request >>> >>> Does this mean that there is an incoming message but the server can't >>> read it successfully? What can induce this problem? Thanks! >>> >> >> These are probably connection attempts that happen to be on the tcp port >> where opensips is listening. >> >> They are probably script kiddies sending http/https/ssh/whatever to >> random ports >> >> -giovanni >> -- >> Sincerely, >> >> Giovanni Maruzzelli >> OpenTelecom.IT >> cell: +39 347 266 56 18 >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
