BIND 10 #1731: noisy output when module not found by xfrout

BIND 10 Development do-not-reply at isc.org
Wed Feb 29 16:11:31 UTC 2012


#1731: noisy output when module not found by xfrout
-------------------------------+-----------------------------------------
            Reporter:  jreed   |                        Owner:
                Type:  defect  |                       Status:  new
            Priority:  minor   |                    Milestone:  New Tasks
           Component:  xfrout  |                     Keywords:
           Sensitive:  0       |              Defect Severity:  N/A
         Sub-Project:  Core    |  Feature Depending on Ticket:
Estimated Difficulty:  0       |          Add Hours to Ticket:  0
         Total Hours:  0       |                    Internal?:  0
-------------------------------+-----------------------------------------
 This is caused by #1728.

 {{{

 2012-02-29 15:27:32.892 INFO  [b10-boss.boss] BIND10_STARTUP_COMPLETE BIND
 10 started
 Traceback (most recent call last):
 2012-02-29 15:27:33.282  File
 "/home/jreed/src/bind10/src/bin/xfrout/b10-xfrout", line 52, in <module>
  DEBUG    from isc.acl.acl import ACCEPT, REJECT, DROP, LoaderError
  [  File "/home/jreed/src/bind10/src/lib/python/isc/acl/__init__.py", line
 11, in <module>
 b10-auth.datasrc    import isc.acl.acl
 ]   File "/home/jreed/src/bind10/src/lib/python/isc/acl/acl.py", line 29,
 in <module>
 DATASRC_CACHE_CREATE creating the hotspot cache    from acl import *

 ImportError: No module named acl
 ...
 2012-02-29 15:27:33.582 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process
 1537 of b10-xfrout ended with status 256
 2012-02-29 15:27:33.582 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
 component b10-xfrout (pid 1537) failed with 256 exit status
 }}}

 But I am opening a new ticket as this happened when BIND 10 was actually
 running and this repeated again when xfrout was started again by boss.

 I am opening this ticket because I think this is too noisy for admin to
 have dumped to screen.

 Maybe install should check issue at install time (I didn't full check as I
 hit some other issues). Or maybe the runtime detection should be cleaner.

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


More information about the bind10-tickets mailing list