BIND 10 #711: starting to use --user
BIND 10 Development
do-not-reply at isc.org
Tue Dec 4 15:17:53 UTC 2012
#711: starting to use --user
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: Next-
Component: Boss of BIND | Sprint-Proposed
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: High
Estimated Difficulty: close? | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jreed):
For last release:
{{{
[jreed at bind10-testing1 dnsbench]$ sudo
work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10
--user nobody
2012-12-04 10:09:56.608 INFO [b10-boss.boss] BIND10_STARTING starting
BIND10: bind10 20110223 (BIND 10 20120817)
2012-12-04 10:09:56.609 INFO [b10-boss.boss] BIND10_CONFIGURATOR_START
bind10 component configurator is starting up
2012-12-04 10:09:56.609 INFO [b10-boss.boss] BIND10_COMPONENT_START
component Socket creator is starting
2012-12-04 10:09:56.612 INFO [b10-boss.boss] BIND10_SOCKCREATOR_INIT
initializing socket creator parser
2012-12-04 10:09:56.612 INFO [b10-boss.boss] BIND10_SETGID setting GID to
99
2012-12-04 10:09:56.612 INFO [b10-boss.boss] BIND10_SETUID setting UID to
99
2012-12-04 10:09:56.612 INFO [b10-boss.boss] BIND10_COMPONENT_START
component msgq is starting
2012-12-04 10:09:56.612 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-msgq
2012-12-04 10:10:01.683 ERROR [b10-boss.boss] BIND10_CONNECTING_TO_CC_FAIL
failed to connect to configuration/command channel; try -v to see output
from msgq
2012-12-04 10:10:01.683 ERROR [b10-boss.boss]
BIND10_COMPONENT_START_EXCEPTION component msgq failed to start: Unable to
connect to c-channel after 5 seconds
2012-12-04 10:10:01.683 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
component msgq (pid None) failed: unknown condition
}}}
It needs to give some hints here. (Like lack of permission.)
{{{
2012-12-04 10:10:01.683 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
component msgq is required to run and failed
2012-12-04 10:10:01.683 ERROR [b10-boss.boss]
BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 1
of 3 done
2012-12-04 10:10:01.683 INFO [b10-boss.boss] BIND10_KILLING_ALL_PROCESSES
killing all started processes
2012-12-04 10:10:01.683 INFO [b10-boss.boss] BIND10_SEND_SIGKILL sending
SIGKILL to Socket creator (PID 29973)
2012-12-04 10:10:01.683 WARN [b10-boss.boss] BIND10_SOCKCREATOR_KILL
killing the socket creator
2012-12-04 10:10:01.683 INFO [b10-boss.boss] BIND10_SEND_SIGNAL_FAIL
sending SIGKILL to Socket creator (PID 29973) failed: [Errno 1] Operation
not permitted
2012-12-04 10:10:01.684 FATAL [b10-boss.boss] BIND10_STARTUP_ERROR error
during startup: Unable to start b10-msgq: Component failed during startup
}}}
(Unrelated to ticket but why SIGKILL sent to sock creator versus other
method?)
Notice an addition FATAL too. Seems strange to have two FATAL, but I guess
it is okay.
I run it again adding the -m switch:
{{{
[jreed at bind10-testing1 dnsbench]$ sudo
work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10
--user nobody -m /tmp/msgq
Password:
2012-12-04 10:16:11.926 INFO [b10-boss.boss] BIND10_STARTING starting
BIND10: bind10 20110223 (BIND 10 20120817)
2012-12-04 10:16:11.926 INFO [b10-boss.boss] BIND10_CONFIGURATOR_START
bind10 component configurator is starting up
2012-12-04 10:16:11.926 INFO [b10-boss.boss] BIND10_COMPONENT_START
component Socket creator is starting
2012-12-04 10:16:11.929 INFO [b10-boss.boss] BIND10_SOCKCREATOR_INIT
initializing socket creator parser
2012-12-04 10:16:11.930 INFO [b10-boss.boss] BIND10_SETGID setting GID to
99
2012-12-04 10:16:11.930 INFO [b10-boss.boss] BIND10_SETUID setting UID to
99
2012-12-04 10:16:11.930 INFO [b10-boss.boss] BIND10_COMPONENT_START
component msgq is starting
2012-12-04 10:16:11.930 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-msgq
2012-12-04 10:16:12.134 INFO [b10-boss.boss] BIND10_COMPONENT_START
component cfgmgr is starting
2012-12-04 10:16:12.134 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-cfgmgr
Traceback (most recent call last):
File
"/home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/libexec/bind10-devel/b10-cfgmgr",
line 131, in <module>
sys.exit(main())
File
"/home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/libexec/bind10-devel/b10-cfgmgr",
line 115, in main
cm.read_config()
File
"/home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/lib/python3.1
/site-packages/isc/config/cfgmgr.py", line 314, in read_config
self.\
File
"/home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/lib/python3.1
/site-packages/isc/config/cfgmgr.py", line 84, in read_from_file
logger.info(CFGMGR_CONFIG_FILE, config.db_filename)
RuntimeError: Unable to use interprocess sync lockfile (Permission
denied):
/home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/var/bind10-devel/logger_lockfile
2012-12-04 10:16:21.339 ERROR [b10-boss.boss]
BIND10_COMPONENT_START_EXCEPTION component cfgmgr failed to start:
Configuration manager process has not started
2012-12-04 10:16:21.339 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
component cfgmgr (pid None) failed: unknown condition
2012-12-04 10:16:21.339 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
component cfgmgr is required to run and failed
2012-12-04 10:16:21.339 ERROR [b10-boss.boss]
BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 2
of 3 done
2012-12-04 10:16:21.339 INFO [b10-boss.boss] BIND10_KILLING_ALL_PROCESSES
killing all started processes
2012-12-04 10:16:21.339 INFO [b10-boss.boss] BIND10_SEND_SIGKILL sending
SIGKILL to Socket creator (PID 30009)
2012-12-04 10:16:21.340 WARN [b10-boss.boss] BIND10_SOCKCREATOR_KILL
killing the socket creator
2012-12-04 10:16:21.340 INFO [b10-boss.boss] BIND10_SEND_SIGNAL_FAIL
sending SIGKILL to Socket creator (PID 30009) failed: [Errno 1] Operation
not permitted
2012-12-04 10:16:21.340 INFO [b10-boss.boss] BIND10_SEND_SIGKILL sending
SIGKILL to msgq (PID 30010)
2012-12-04 10:16:21.340 FATAL [b10-boss.boss] BIND10_STARTUP_ERROR error
during startup: Unable to start b10-cfgmgr: Component failed during
startup
}}}
That should have a cleaner output.
--
Ticket URL: <https://bind10.isc.org/ticket/711#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list