We have recently upgraded from 5.6.4 to 5.7.4. No change in the KAMAILIO configuration.
On all upgraded servers we are now getting this message in the logs for every destination when the dispatcher sends out OPTIONS to destinations listed in the dispatcher list:
WARNING: <core> [core/tcp_main.c:1301]: find_listening_sock_info(): binding to source address X.X.X.X:YYYY failed: Address already in use [98]
The X.X.X.X being the servers IP address and YYYY being the servers listening port for tcp and/or tls.
It's not consistent. For some servers it's every time OPTIONS is sent. For others it's just now and then. udp destinations have no issues.
There are no other processes occupying these ports. Changing the listening port on the KAMAILIO also results in the new port reported as in use.
Dispatcher OPTIONS still seems to work for both tcp and tls. Unsurprisingly using a dynamic, unprivileged port > 1023 and not the server port as the source port, as it shouldn't. The packages are sendt and a reply is registered. Inbound OPTIONS are processed as expected by KAMAILIO on the listening port.
Have I missed something transitioning from 5.6 -> 5.7, or is this a bug?
Relevant config: modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 2) modparam("dispatcher", "ds_ping_interval", 120) modparam("dispatcher", "ds_ping_from", "sip:ping@xxxxxx.xxx") modparam("dispatcher", "ds_ping_latency_stats", 1)
OS: Debian Bullseye Kamailio installed from https://deb.kamailio.org/kamailio57 bullseye
Best regards, Jardar Leira
Hello,
we also observed this going from an older release to 5.7.x this week. It seems to be harmless, but its generating indeed a lot of warnings.
Cheers,
Henning
-----Original Message----- From: Jardar Leira via sr-users sr-users@lists.kamailio.org Sent: Donnerstag, 15. Februar 2024 22:30 To: sr-users@lists.kamailio.org Cc: Jardar Leira jardar.leira@sikt.no Subject: [SR-Users] Dispatcher ping: "binding to source address X.X.X.X:XXXX failed: Address already in use" for TCP and TLS destinations
We have recently upgraded from 5.6.4 to 5.7.4. No change in the KAMAILIO configuration.
On all upgraded servers we are now getting this message in the logs for every destination when the dispatcher sends out OPTIONS to destinations listed in the dispatcher list:
WARNING: <core> [core/tcp_main.c:1301]: find_listening_sock_info(): binding to source address X.X.X.X:YYYY failed: Address already in use [98]
The X.X.X.X being the servers IP address and YYYY being the servers listening port for tcp and/or tls.
It's not consistent. For some servers it's every time OPTIONS is sent. For others it's just now and then. udp destinations have no issues.
There are no other processes occupying these ports. Changing the listening port on the KAMAILIO also results in the new port reported as in use.
Dispatcher OPTIONS still seems to work for both tcp and tls. Unsurprisingly using a dynamic, unprivileged port > 1023 and not the server port as the source port, as it shouldn't. The packages are sendt and a reply is registered. Inbound OPTIONS are processed as expected by KAMAILIO on the listening port.
Have I missed something transitioning from 5.6 -> 5.7, or is this a bug?
Relevant config: modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 2) modparam("dispatcher", "ds_ping_interval", 120) modparam("dispatcher", "ds_ping_from", "sip:ping@xxxxxx.xxx") modparam("dispatcher", "ds_ping_latency_stats", 1)
OS: Debian Bullseye Kamailio installed from https://deb.kamailio.org/kamailio57 bullseye
Best regards, Jardar Leira
Hello,
+1
Kamailio 5.7.3 logs warnings on every call to *t_relay()*, not just dispatcher OPTIONS. When *tcp_reuse_port=yes* there are no warnings, but in this case the client sends requests from the server port.
Is there another W/A?
пт, 16 февр. 2024 г. в 15:52, Henning Westerholt via sr-users < sr-users@lists.kamailio.org>:
Hello,
we also observed this going from an older release to 5.7.x this week. It seems to be harmless, but its generating indeed a lot of warnings.
Cheers,
Henning
-----Original Message----- From: Jardar Leira via sr-users sr-users@lists.kamailio.org Sent: Donnerstag, 15. Februar 2024 22:30 To: sr-users@lists.kamailio.org Cc: Jardar Leira jardar.leira@sikt.no Subject: [SR-Users] Dispatcher ping: "binding to source address
X.X.X.X:XXXX
failed: Address already in use" for TCP and TLS destinations
We have recently upgraded from 5.6.4 to 5.7.4. No change in the KAMAILIO configuration.
On all upgraded servers we are now getting this message in the logs for
every
destination when the dispatcher sends out OPTIONS to destinations listed
in
the dispatcher list:
WARNING: <core> [core/tcp_main.c:1301]: find_listening_sock_info(): binding to source address X.X.X.X:YYYY failed: Address already in use
[98]
The X.X.X.X being the servers IP address and YYYY being the servers
listening
port for tcp and/or tls.
It's not consistent. For some servers it's every time OPTIONS is sent. For others it's just now and then. udp destinations have no issues.
There are no other processes occupying these ports. Changing the
listening
port on the KAMAILIO also results in the new port reported as in use.
Dispatcher OPTIONS still seems to work for both tcp and tls. Unsurprisingly using a dynamic, unprivileged port > 1023 and not the
server
port as the source port, as it shouldn't. The packages are sendt and a
reply is
registered. Inbound OPTIONS are processed as expected by KAMAILIO on the listening port.
Have I missed something transitioning from 5.6 -> 5.7, or is this a bug?
Relevant config: modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 2) modparam("dispatcher", "ds_ping_interval",
modparam("dispatcher", "ds_ping_from", "sip:ping@xxxxxx.xxx") modparam("dispatcher", "ds_ping_latency_stats", 1)
OS: Debian Bullseye Kamailio installed from https://deb.kamailio.org/kamailio57 bullseye
Best regards, Jardar Leira
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: