BIND 10 #2067: cfgmgr cannot open log lock file if started with -u
BIND 10 Development
do-not-reply at isc.org
Tue Jun 19 17:48:43 UTC 2012
#2067: cfgmgr cannot open log lock file if started with -u
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: defect | Status: new
Priority: very high | Milestone:
Component: logging | Sprint-20120703
Sensitive: 0 | Keywords:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Starting the latest master version of BIND 10 with '-u bind' failed:
{{{
2012-06-19 09:37:17.687 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-cfgmgr
Traceback (most recent call last):
File "/home/jinmei/opt/libexec/bind10-devel/b10-cfgmgr", line 137, in
<module>
sys.exit(main())
File "/home/jinmei/opt/libexec/bind10-devel/b10-cfgmgr", line 121, in
main
cm.read_config()
File "/home/jinmei/opt/lib/python3.1/site-
packages/isc/config/cfgmgr.py", line 314, in read_config
self.\
File "/home/jinmei/opt/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:
/home/jinmei/opt/var/bind10-devel/logger_lockfile
}}}
This is because the group ID of cfgmgr (and originally bind10 for that
matter) hasn't been changed while the lock file was opened when bind
10 was a root.
I believe this is critical and should be fixed before the release. So
I'm pushing it to the current sprint.
--
Ticket URL: <http://bind10.isc.org/ticket/2067>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list