Hi Duarte,

You can enable a filter on the nathelper module to help with this
https://www.kamailio.org/docs/modules/5.2.x/modules/nathelper.html#nathelper.p.filter_server_id

Check the similar setting for usrloc if you're using cache mode
https://www.kamailio.org/docs/modules/5.2.x/modules/usrloc.html#usrloc.p.server_id_filter

Cheers,
Boden

On Wed, 8 May 2019, at 10:06 PM, Duarte Rocha wrote:
Greetings,

I have two Machines with Kamailio in a High Availability  (HA) configuration. Both machines are active and processing calls and both have one HA IP that can jump to the other machine in case of failure.

I also have probing for NAPs configured with each IP as the socket. 

So, in each machine i have this configuration : 

listen=udp:HA_Address1
listen=udp:HA_Address2

NAP 1 being probed from socket HA_Address1
NAP 1 being probed from socket HA_Address2

I also have /proc/sys/net/ipv4/ip_nonlocal_bind with value 1.

Everything works correctly with this configuration. However when the probing is sent for the NAP' my logs get filled with the same error messages.

udp_send(): sendto(sock, buf: 0x7f2d4c91fa18, len: 340, 0, dst: (xxx.xxx.xxx.xxx:xxx), tolen: 16) - err: Invalid argument (22)
CRITICAL: <core> [core/udp_server.c:602]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net
ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed


The error happens because it is trying to probe a NAP using a socket that isn't active at the moment in the machine.

Is there a way for this error not to be logged or be disabled without reducing Log Level to suppress CRITICAL errors?
I think this is a standard High Availability configuration. Is there some setting that can disable this kind of errors?

Best Regards,

Duarte Rocha
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users