From: JINMEI Tatuya Date: Thu, 8 Nov 2012 06:35:25 +0000 (-0800) Subject: [2447] improved detailed description of CONFIG_LOAD_FAIL ref'ing sock failure. X-Git-Tag: trac2487_base~1^2~31^2~1^2^2~7 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0590b6d313c25728cb13a8738ba3ceeb4e6cdd2c;p=thirdparty%2Fkea.git [2447] improved detailed description of CONFIG_LOAD_FAIL ref'ing sock failure. it even suggests restarting as a root. --- diff --git a/src/bin/auth/auth_messages.mes b/src/bin/auth/auth_messages.mes index 221d1221eb..37804995f7 100644 --- a/src/bin/auth/auth_messages.mes +++ b/src/bin/auth/auth_messages.mes @@ -47,10 +47,15 @@ available. It is issued during server startup is an indication that the initialization is proceeding normally. % AUTH_CONFIG_LOAD_FAIL load of configuration failed: %1 -An attempt to configure the server with information from the configuration -database during the startup sequence has failed. (The reason for -the failure is given in the message.) The server will continue its -initialization although it may not be configured in the desired way. +An attempt to configure the server with information from the +configuration database during the startup sequence has failed. The +server will continue its initialization although it may not be +configured in the desired way. The reason for the failure is given in +the message. One common reason is that the server failed to acquire a +socket bound to a privileged port (53 for DNS). In that case the +reason in the log message should show something like "permission +denied", and the solution would be to restart BIND 10 as a super +(root) user. % AUTH_CONFIG_UPDATE_FAIL update of configuration failed: %1 At attempt to update the configuration the server with information