the specified address on the given protocol. The number of the system
error that caused the problem is given in the message.
-% ASIODNS_UDP_SYNC_SEND_FAIL Error sending UDP packet to %1: %2
+% ASIODNS_UDP_ASYNC_SEND_FAIL Error sending UDP packet to %1: %2
The low-level ASIO library reported an error when trying to send a UDP
-packet in synchronous UDP mode. This can be any error reported by send_to(),
-and can indicate problems such as too high a load on the network, or a
-problem in the underlying library or system.
+packet in asynchronous UDP mode. This can be any error reported by
+send_to(), and can indicate problems such as too high a load on the network,
+or a problem in the underlying library or system.
This packet is dropped and will not be sent, but service should resume
normally.
If you see a single occurrence of this message, it probably does not
indicate any significant problem, but if it is logged often, it is probably
a good idea to inspect your network traffic.
+% ASIODNS_UDP_SYNC_SEND_FAIL Error sending UDP packet to %1: %2
+The low-level ASIO library reported an error when trying to send a UDP
+packet in synchronous UDP mode. See ASIODNS_UDP_ASYNC_SEND_FAIL for
+more information.
+
% ASIODNS_UNKNOWN_ORIGIN unknown origin for ASIO error code %1 (protocol: %2, address %3)
An internal consistency check on the origin of a message from the
asynchronous I/O module failed. This may indicate an internal error;
CORO_YIELD data_->socket_->async_send_to(
buffer(data_->respbuf_->getData(), data_->respbuf_->getLength()),
*data_->sender_, *this);
+ if (ec) {
+ LOG_ERROR(logger, ASIODNS_UDP_ASYNC_SEND_FAIL).
+ arg(data_->sender_->address().to_string()).
+ arg(ec.message());
+ }
}
}