BIND 10 #711: starting to use --user

[BIND 10 Development]

#711: starting to use --user
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  Boss of BIND  |  Sprint-20121218
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  High
Estimated Difficulty:  3             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jreed):

 More problems:

 {{{
 [jreed at bind10-testing1 dnsbench]$ sudo env
 B10_LOCKFILE_DIR_FROM_BUILD=/tmp BIND10_DDNS_SOCKET_FILE=/tmp/ddns
 work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10
 --user nobody -m /tmp/msgq
 2012-12-04 11:14:05.029 INFO  [b10-boss.boss] BIND10_STARTING starting
 BIND10: bind10 20110223 (BIND 10 20120817)
 2012-12-04 11:14:05.030 INFO  [b10-boss.boss] BIND10_CONFIGURATOR_START
 bind10 component configurator is starting up
 2012-12-04 11:14:05.030 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component Socket creator is starting
 2012-12-04 11:14:05.033 INFO  [b10-boss.boss] BIND10_SOCKCREATOR_INIT
 initializing socket creator parser
 2012-12-04 11:14:05.033 INFO  [b10-boss.boss] BIND10_SETGID setting GID to
 99
 2012-12-04 11:14:05.033 INFO  [b10-boss.boss] BIND10_SETUID setting UID to
 99
 2012-12-04 11:14:05.033 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component msgq is starting
 2012-12-04 11:14:05.033 INFO  [b10-boss.boss] BIND10_STARTING_PROCESS
 starting process b10-msgq
 2012-12-04 11:14:05.236 INFO  [b10-boss.boss] BIND10_COMPONENT_START
 component cfgmgr is starting
 2012-12-04 11:14:05.237 INFO  [b10-boss.boss] BIND10_STARTING_PROCESS
 starting process b10-cfgmgr
 2012-12-04 11:14:05.380 INFO  [b10-cfgmgr.cfgmgr] CFGMGR_CONFIG_FILE
 Configuration manager starting with configuration file:
 /home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/var/bind10-devel/b10-config.db
 2012-12-04 11:14:05.381 FATAL [b10-cfgmgr.cfgmgr] CFGMGR_DATA_READ_ERROR
 error reading configuration database from disk: Can't read configuration
 file: [Errno 13] Permission denied:
 '/home/jreed/dnsbench/work/origin/bind10-20121115-release/20121126190544/install/var/bind10-devel/b10-config.db'
 2012-12-04 11:14:14.386 ERROR [b10-boss.boss]
 BIND10_COMPONENT_START_EXCEPTION component cfgmgr failed to start:
 Configuration manager process has not started
 2012-12-04 11:14:14.386 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
 component cfgmgr (pid None) failed: unknown condition
 2012-12-04 11:14:14.386 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
 component cfgmgr is required to run and failed
 2012-12-04 11:14:14.386 ERROR [b10-boss.boss]
 BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 2
 of 3 done
 2012-12-04 11:14:14.386 INFO  [b10-boss.boss] BIND10_KILLING_ALL_PROCESSES
 killing all started processes
 2012-12-04 11:14:14.386 INFO  [b10-boss.boss] BIND10_SEND_SIGKILL sending
 SIGKILL to msgq (PID 30224)
 2012-12-04 11:14:14.387 INFO  [b10-boss.boss] BIND10_SEND_SIGKILL sending
 SIGKILL to Socket creator (PID 30223)
 2012-12-04 11:14:14.387 WARN  [b10-boss.boss] BIND10_SOCKCREATOR_KILL
 killing the socket creator
 2012-12-04 11:14:14.387 INFO  [b10-boss.boss] BIND10_SEND_SIGNAL_FAIL
 sending SIGKILL to Socket creator (PID 30223) failed: [Errno 1] Operation
 not permitted
 2012-12-04 11:14:14.387 FATAL [b10-boss.boss] BIND10_STARTUP_ERROR error
 during startup: Unable to start b10-cfgmgr: Component failed during
 startup
 Traceback (most recent call last):
   File
 "work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10",
 line 1216, in main
     sys.exit(1)
 SystemExit: 1

 During handling of the above exception, another exception occurred:
 Traceback (most recent call last):
   File
 "work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10",
 line 1236, in <module>
     main()
   File
 "work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10",
 line 1230, in main
     remove_lock_files()
   File
 "work/origin/bind10-20121115-release/20121126190544/install/sbin/bind10",
 line 1133, in remove_lock_files
     os.unlink(fname)
 OSError: [Errno 1] Operation not permitted: '/tmp/logger_lockfile'

 [jreed at bind10-testing1 dnsbench]$ ls -l /tmp/logger_lockfile
 -rw-rw---- 1 root root 0 Dec  4 11:14 /tmp/logger_lockfile
 }}}

 We need a lettuce test for -u. Which means we need root privilege to run a
 test. We can add this an optional system test. Another ticket can be
 created for this.

-- 
Ticket URL: <http://bind10.isc.org/ticket/711#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development