Commit 1a80b1dd authored by Mukund Sivaraman's avatar Mukund Sivaraman
Browse files

[2672] Rename _ERR suffix to _ERROR in message IDs

parent a12aed4b
......@@ -411,7 +411,7 @@ class MsgQ:
if isinstance(err, MsgQCloseOnReceive) and not err.partial_read:
logger.debug(TRACE_BASIC, MSGQ_CLOSE_ON_RECV, fd)
else:
logger.error(MSGQ_RECV_ERR, fd, err)
logger.error(MSGQ_RECV_ERROR, fd, err)
self.kill_socket(fd, sock)
return
......@@ -419,7 +419,7 @@ class MsgQ:
routingmsg = isc.cc.message.from_wire(routing)
except DecodeError as err:
self.kill_socket(fd, sock)
logger.error(MSGQ_HDR_DECODE_ERR, fd, err)
logger.error(MSGQ_HDR_DECODE_ERROR, fd, err)
return
self.process_command(fd, sock, routingmsg, data)
......@@ -492,7 +492,7 @@ class MsgQ:
if e.errno == errno.EPIPE:
logger.warn(MSGQ_CLOSE_ON_SEND, sock.fileno())
else:
logger.error(MSGQ_SEND_ERR, sock.fileno(),
logger.error(MSGQ_SEND_ERROR, sock.fileno(),
errno.errorcode[e.errno])
self.kill_socket(sock.fileno(), sock)
return None
......@@ -620,7 +620,7 @@ class MsgQ:
if err.args[0] == errno.EINTR:
events = []
else:
logger.fatal(MSGQ_POLL_ERR, err)
logger.fatal(MSGQ_POLL_ERROR, err)
break
with self.__lock:
for (fd, event) in events:
......
......@@ -62,7 +62,7 @@ Debug message. The message queue received a configuration update, handling it.
% MSGQ_EXITING exiting
The msgq daemon is exiting.
% MSGQ_HDR_DECODE_ERR Error decoding header received from socket %1: %2
% MSGQ_HDR_DECODE_ERROR Error decoding header received from socket %1: %2
The socket with mentioned file descriptor sent a packet. However, it was not
possible to decode the routing header of the packet. The packet is ignored.
This may be caused by a programmer error (one of the components sending invalid
......@@ -85,7 +85,7 @@ Debug message. The listener is trying to open a listening socket.
Debug message. The message queue successfully opened a listening socket and
waits for incoming connections.
% MSGQ_POLL_ERR Error while polling for events: %1
% MSGQ_POLL_ERROR Error while polling for events: %1
A low-level error happened when waiting for events, the error is logged. The
reason for this varies, but it usually means the system is short on some
resources.
......@@ -96,7 +96,7 @@ happen and it is either a programmer error or OS bug. The event is ignored. The
number noted as the event is the raw encoded value, which might be useful to
the authors when figuring the problem out.
% MSGQ_RECV_ERR Error reading from socket %1: %2
% MSGQ_RECV_ERROR Error reading from socket %1: %2
There was a low-level error when reading from a socket. The error is logged and
the corresponding socket is dropped. The errors include receiving
broken or (non empty but) incomplete data. In either case it usually suggests
......@@ -119,7 +119,7 @@ on shutdown unless there's really something unexpected.
% MSGQ_RECV_HDR Received header: %1
Debug message. This message includes the whole routing header of a packet.
% MSGQ_SEND_ERR Error while sending to socket %1: %2
% MSGQ_SEND_ERROR Error while sending to socket %1: %2
There was a low-level error when sending data to a socket. The error is logged
and the corresponding socket is dropped.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment