BIND 10 #711: starting to use --user
BIND 10 Development
do-not-reply at isc.org
Tue Feb 28 12:03:31 UTC 2012
#711: starting to use --user
--------------------------------------------+-----------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Unclassified | Resolution:
Keywords: | Sensitive: 0
Defect Severity: High | Sub-Project: Core
Feature Depending on Ticket: | Estimated Difficulty: 0.0
Add Hours to Ticket: 0 | Total Hours: 0
Internal?: 0 |
--------------------------------------------+-----------------------------
Changes (by shane):
* subproject: => Core
* severity: => High
Comment:
This appears to be the same problem now, although the output is quite
different:
{{{
[shane at shane-desktop sbin]$ sudo ./bind10 -u shane
2012-02-28 13:00:42.284 INFO [b10-boss.boss] BIND10_STARTING starting
BIND10: bind10 20110223 (BIND 10 20120127)
2012-02-28 13:00:42.284 INFO [b10-boss.boss] BIND10_CONFIGURATOR_START
bind10 component configurator is starting up
2012-02-28 13:00:42.284 INFO [b10-boss.boss] BIND10_COMPONENT_START
component Socket creator is starting
2012-02-28 13:00:42.289 INFO [b10-boss.boss] BIND10_SOCKCREATOR_INIT
initializing socket creator parser
2012-02-28 13:00:42.289 INFO [b10-boss.boss] BIND10_SETUID setting UID to
500
2012-02-28 13:00:42.289 INFO [b10-boss.boss] BIND10_COMPONENT_START
component msgq is starting
2012-02-28 13:00:42.289 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-msgq
2012-02-28 13:00:42.497 INFO [b10-boss.boss] BIND10_COMPONENT_START
component cfgmgr is starting
2012-02-28 13:00:42.498 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-cfgmgr
2012-02-28 13:00:42.604 FATAL [b10-cfgmgr.cfgmgr] CFGMGR_DATA_READ_ERROR
error reading configuration database from disk: Can't read configuration
file: [Errno 13] Permission denied:
'/tmp/bind10/var/bind10-devel/b10-config.db'
2012-02-28 13:00:51.629 ERROR [b10-boss.boss]
BIND10_COMPONENT_START_EXCEPTION component cfgmgr failed to start:
Configuration manager process has not started
2012-02-28 13:00:51.629 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
component cfgmgr (pid None) failed with unknown exit status
2012-02-28 13:00:51.629 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
component cfgmgr is required to run and failed
2012-02-28 13:00:51.629 ERROR [b10-boss.boss]
BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 2
of 3 done
2012-02-28 13:00:51.629 INFO [b10-boss.boss] BIND10_KILLING_ALL_PROCESSES
killing all started processes
2012-02-28 13:00:51.629 INFO [b10-boss.boss] BIND10_KILL_PROCESS killing
process Socket creator
2012-02-28 13:00:51.629 WARN [b10-boss.boss] BIND10_SOCKCREATOR_KILL
killing the socket creator
Traceback (most recent call last):
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 165, in start
self._start_internal()
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 403, in _start_internal
procinfo = self._start_func()
File "./bind10", line 484, in start_cfgmgr
raise ProcessStartError("Configuration manager process has not
started")
__main__.ProcessStartError: Configuration manager process has not started
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./bind10", line 646, in startup
self.start_all_components()
File "./bind10", line 607, in start_all_components
self._component_configurator.startup(self.__core_components)
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 504, in startup
self.__reconfigure_internal(self._components, configuration)
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 492, in __reconfigure_internal
self._run_plan(self._build_plan(old, new))
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 633, in _run_plan
component.start()
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 168, in start
self.failed(None)
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/component.py", line 222, in failed
self._boss.component_shutdown(1)
File "./bind10", line 682, in component_shutdown
raise Exception("Component failed during startup");
Exception: Component failed during startup
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./bind10", line 1193, in <module>
main()
File "./bind10", line 1171, in main
startup_result = boss_of_bind.startup()
File "./bind10", line 648, in startup
self.kill_started_components()
File "./bind10", line 351, in kill_started_components
self.components[pid].kill(True)
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/special_component.py", line 68, in kill
self.__creator.kill()
File "/tmp/bind10/lib64/python3.2/site-
packages/isc/bind10/sockcreator.py", line 239, in kill
self.__process.kill()
File "/usr/lib64/python3.2/subprocess.py", line 1573, in kill
self.send_signal(signal.SIGKILL)
File "/usr/lib64/python3.2/subprocess.py", line 1563, in send_signal
os.kill(self.pid, sig)
OSError: [Errno 1] Operation not permitted
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/711#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list