cc_messages.mes 5.09 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
# Copyright (C) 2010  Internet Systems Consortium, Inc. ("ISC")
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#
# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
# AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.

$NAMESPACE isc::cc
16

17
% CC_ASYNC_READ_FAILED asynchronous read failed (error code = %1)
18 19
This marks a low level error, we tried to read data from the message queue
daemon asynchronously, but the ASIO library returned an error.
20

21
% CC_CONN_ERROR error connecting to message queue (%1)
22 23 24 25
It is impossible to reach the message queue daemon for the reason given. It
is unlikely there'll be reason for whatever program this currently is to
continue running, as the communication with the rest of BIND 10 is vital
for the components.
26

27
% CC_DISCONNECT disconnecting from message queue daemon
28 29
The library is disconnecting from the message queue daemon. This debug message
indicates that the program is trying to shut down gracefully.
30

31
% CC_ESTABLISH trying to establish connection with message queue daemon at %1
32 33
This debug message indicates that the command channel library is about to
connect to the message queue daemon, which should be listening on the UNIX-domain
34
socket listed in the output.
35

36
% CC_ESTABLISHED successfully connected to message queue daemon
37 38
This debug message indicates that the connection was successfully made, this
should follow CC_ESTABLISH.
39

40
% CC_GROUP_RECEIVE trying to receive a message
41 42
Debug message, noting that a message is expected to come over the command
channel.
43

44
% CC_GROUP_RECEIVED message arrived ('%1', '%2')
45 46 47
Debug message, noting that we successfully received a message (its envelope and
payload listed). This follows CC_GROUP_RECEIVE, but might happen some time
later, depending if we waited for it or just polled.
48

49
% CC_GROUP_SEND sending message '%1' to group '%2'
50
Debug message, we're about to send a message over the command channel.
51 52

% CC_INVALID_LENGTHS invalid length parameters (%1, %2)
53 54 55
This happens when garbage comes over the command channel or some kind of
confusion happens in the program. The data received from the socket make no
sense if we interpret it as lengths of message. The first one is total length
56 57
of the message; the second is the length of the header. The header
and its length (2 bytes) is counted in the total length.
58

59
% CC_LENGTH_NOT_READY length not ready
60
There should be data representing the length of message on the socket, but it
61
is not there.
62

63 64 65 66
% CC_LNAME_RECEIVED received local name: %1
Debug message: the local module received its unique identifier (name)
from msgq on completion of establishing the session with msgq.

67
% CC_NO_MESSAGE no message ready to be received yet
68 69
The program polled for incoming messages, but there was no message waiting.
This is a debug message which may happen only after CC_GROUP_RECEIVE.
70

71
% CC_NO_MSGQ unable to connect to message queue (%1)
72 73
It isn't possible to connect to the message queue daemon, for reason listed.
It is unlikely any program will be able continue without the communication.
74

75
% CC_READ_ERROR error reading data from command channel (%1)
76 77
A low level error happened when the library tried to read data from the
command channel socket. The reason is listed.
78

79
% CC_READ_EXCEPTION error reading data from command channel (%1)
80 81
We received an exception while trying to read data from the command
channel socket. The reason is listed.
82

83
% CC_REPLY replying to message from '%1' with '%2'
84 85
Debug message, noting we're sending a response to the original message
with the given envelope.
86

87
% CC_SET_TIMEOUT setting timeout to %1ms
88 89
Debug message. A timeout for which the program is willing to wait for a reply
is being set.
90

91
% CC_START_READ starting asynchronous read
92 93
Debug message. From now on, when a message (or command) comes, it'll wake the
program and the library will automatically pass it over to correct place.
94

95
% CC_SUBSCRIBE subscribing to communication group %1
96
Debug message. The program wants to receive messages addressed to this group.
97

98
% CC_TIMEOUT timeout reading data from command channel
99 100
The program waited too long for data from the command channel (usually when it
sent a query to different program and it didn't answer for whatever reason).
101

102
% CC_UNSUBSCRIBE unsubscribing from communication group %1
103 104
Debug message. The program no longer wants to receive messages addressed to
this group.
105

106
% CC_WRITE_ERROR error writing data to command channel (%1)
107 108
A low level error happened when the library tried to write data to the command
channel socket.
109 110

% CC_ZERO_LENGTH invalid message length (0)
111
The library received a message length being zero, which makes no sense, since
112
all messages must contain at least the envelope.