### Description
Hi!
We are in the progress of upgrading from Kamailio 5.5 to 5.8. During our
testing we have noticed a new error being reported from Kamailio. We don’t see
any other errors following it.
```jsx
/usr/sbin/kamailio[201]: CRITICAL: <core> [core/tcp_main.c:5544]:
tcp_timer_check_connections(): message processing timeout on connection id:
67896 (state: 3) - closing
```
It does seem to be [new
code](https://github.com/kamailio/kamailio/blob/master/src/core/tcp_main.c#L5497)
in Kamailio reporting this issue.
Given that this is a fairly expected thing, cleaning up a connection which
receives no traffic within the given time, is there a need for it to be
reported on CRITICAL?
I’d also expect it to be caught by
```
event_route[tcp:timeout] {
xlog("L_INFO","connection $conid timeouts (unanswered keepalives)");
}
```
given that [the
description](https://www.kamailio.org/docs/modules/stable/modules/tcpops.html#idm264)
of this one is `Called for connection timeouts (unanswered keepalives).`.
### Troubleshooting
We don't have any way to reproduce it, we are still investigating it to figure
out the cause. It happens around every 2 hours, so we think there might some
some scheduled test or job running in our test system causing this.
### Additional Information
* **Kamailio Version** - 5.8.3
* **Operating System**: Debian 12 AMI from the AWS Marketplace.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3995
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3...@github.com>_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
