Commit 921405b0 authored by JINMEI Tatuya's avatar JINMEI Tatuya
Browse files

[1539] cleanup: reordered log message

parent a53adb0b
...@@ -255,6 +255,17 @@ processed by the authoritative server has been found to contain an ...@@ -255,6 +255,17 @@ processed by the authoritative server has been found to contain an
unsupported opcode. (The opcode is included in the message.) The server unsupported opcode. (The opcode is included in the message.) The server
will return an error code of NOTIMPL to the sender. will return an error code of NOTIMPL to the sender.
% AUTH_UPDATE_FORWARD_ERROR failed to forward update request from %1: %2
The authoritative server receives a dynamic update request, tried to
forward it to a separate process (which is usually b10-ddns) to handle it,
but it failed. It could be configuration mismatch between b10-auth and
b10-ddns, or it may because update requests are coming too fast and b10-ddns
cannot keep up with the rate, or some system level failure. In either case
this means the BIND 10 system is not working as expected, so the administrator
should look into the cause and address the issue. The log message
includes the client's address (and port), and the error message sent
from the lower layer that detects the failure.
% AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created % AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created
This is a debug message indicating that the authoritative server has This is a debug message indicating that the authoritative server has
created a channel to the XFRIN (Transfer-in) process. It is issued created a channel to the XFRIN (Transfer-in) process. It is issued
...@@ -277,14 +288,3 @@ This is a debug message output during the processing of a NOTIFY ...@@ -277,14 +288,3 @@ This is a debug message output during the processing of a NOTIFY
request. The zone manager component has been informed of the request, request. The zone manager component has been informed of the request,
but has returned an error response (which is included in the message). The but has returned an error response (which is included in the message). The
NOTIFY request will not be honored. NOTIFY request will not be honored.
% AUTH_UPDATE_FORWARD_ERROR failed to forward update request from %1: %2
The authoritative server receives a dynamic update request, tried to
forward it to a separate process (which is usually b10-ddns) to handle it,
but it failed. It could be configuration mismatch between b10-auth and
b10-ddns, or it may because update requests are coming too fast and b10-ddns
cannot keep up with the rate, or some system level failure. In either case
this means the BIND 10 system is not working as expected, so the administrator
should look into the cause and address the issue. The log message
includes the client's address (and port), and the error message sent
from the lower layer that detects the failure.
Supports Markdown
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