|
|
@@ -32,6 +32,68 @@ started according to the configuration.
|
|
|
An error was encountered when the boss module specified
|
|
|
statistics data which is invalid for the boss specification file.
|
|
|
|
|
|
+% BIND10_COMPONENT_FAILED component %1 (pid %2) failed with %3 exit status
|
|
|
+The process terminated, but the bind10 boss didn't expect it to, which means
|
|
|
+it must have failed.
|
|
|
+
|
|
|
+% BIND10_COMPONENT_RESTART component %1 is about to restart
|
|
|
+The named component failed previously and we will try to restart it to provide
|
|
|
+as flawless service as possible, but it should be investigated what happened,
|
|
|
+as it could happen again.
|
|
|
+
|
|
|
+% BIND10_COMPONENT_START component %1 is starting
|
|
|
+The named component is about to be started by the boss process.
|
|
|
+
|
|
|
+% BIND10_COMPONENT_START_EXCEPTION component %1 failed to start: %2
|
|
|
+An exception (mentioned in the message) happened during the startup of the
|
|
|
+named component. The componet is not considered started and further actions
|
|
|
+will be taken about it.
|
|
|
+
|
|
|
+% BIND10_COMPONENT_STOP component %1 is being stopped
|
|
|
+A component is about to be asked to stop willingly by the boss.
|
|
|
+
|
|
|
+% BIND10_COMPONENT_UNSATISFIED component %1 is required to run and failed
|
|
|
+A component failed for some reason (see previous messages). It is either a core
|
|
|
+component or needed component that was just started. In any case, the system
|
|
|
+can't continue without it and will terminate.
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_BUILD building plan '%1' -> '%2'
|
|
|
+A debug message. This indicates that the configurator is building a plan
|
|
|
+how to change configuration from the older one to newer one. This does no
|
|
|
+real work yet, it just does the planning what needs to be done.
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only %1 of %2 done
|
|
|
+There was an exception during some planned task. The plan will not continue and
|
|
|
+only some tasks of the plan were completed. The rest is aborted. The exception
|
|
|
+will be propagated.
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components
|
|
|
+A different configuration of which components should be running is being
|
|
|
+installed. All components that are no longer needed will be stopped and
|
|
|
+newly introduced ones started. This happens at startup, when the configuration
|
|
|
+is read the first time, or when an operator changes configuration of the boss.
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_RUN running plan of %1 tasks
|
|
|
+A debug message. The configurator is about to execute a plan of actions it
|
|
|
+computed previously.
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_START bind10 component configurator is starting up
|
|
|
+The part that cares about starting and stopping the right component from the
|
|
|
+boss process is starting up. This happens only once at the startup of the
|
|
|
+boss process. It will start the basic set of processes now (the ones boss
|
|
|
+needs to read the configuration), the rest will be started after the
|
|
|
+configuration is known.
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down
|
|
|
+The part that cares about starting and stopping processes in the boss is
|
|
|
+shutting down. All started components will be shut down now (more precisely,
|
|
|
+asked to terminate by their own, if they fail to comply, other parts of
|
|
|
+the boss process will try to force them).
|
|
|
+
|
|
|
+% BIND10_CONFIGURATOR_TASK performing task %1 on %2
|
|
|
+A debug message. The configurator is about to perform one task of the plan it
|
|
|
+is currently executing on the named component.
|
|
|
+
|
|
|
% BIND10_INVALID_USER invalid user: %1
|
|
|
The boss process was started with the -u option, to drop root privileges
|
|
|
and continue running as the specified user, but the user is unknown.
|
JINMEI Tatuya