Hello Arnd,

Thank you for answering me

That would be a solution but i can't use it since i need to be able to specify sockets on a per Nap basis. My listen config has more addresses than those mentioned by me and the sockets are part of the NAP identification. 

The best way to solve this would be something to suppress the error i think. 

A quarta, 8/05/2019, 13:04, Duarte Rocha <duarterocha91@gmail.com> escreveu:
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