Hi devs, The logs of our Kamailio servers are rich for such lines: ``` Oct 28 06:57:35 ip-172-31-0-139 /usr/local/sbin/kamailio[31963]: ERROR: <core> [tcp_read.c:271]: tcp_read_data(): error reading: Connection reset by peer (104) Oct 28 06:57:35 ip-172-31-0-139 /usr/local/sbin/kamailio[31963]: ERROR: <core> [tcp_read.c:1296]: tcp_read_req(): ERROR: tcp_read_req: error reading ```
The servers serve WS, WSS, UDP, TCP and TLS as connection transports. So we cannot figure what happens and if this is really a problem, but we get accused by whoever audits the servers. What could be done to make this more trackable? Or maybe these messages should be suppressed, if there's no way to track them and they don't mean any problem?
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/385
Did you checked what is happening at the time you get the logs, for example using tcpdump ?
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/385#issuecomment-152256316
I pushed a commit to print the source and destination ip of the connections in such log messages, maybe it will help to figure out what device was at the end of the connection and track better what happened. The patch is in master and 4.3 branches.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/385#issuecomment-153759268
Thank you very much, will try it!
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/385#issuecomment-153790683
Closed #385.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/385#event-683448195
Reopen if you get new details to investigate here.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/385#issuecomment-224085732