BIND 10 #2800: Unable to lock logger lockfile

[BIND 10 Development]

#2800: Unable to lock logger lockfile
---------------------------------------+----------------------------------
                   Reporter:  jreed    |                 Owner:
                       Type:  defect   |                Status:  new
                   Priority:  medium   |             Milestone:  New Tasks
                  Component:  logging  |              Keywords:
               CVSS Scoring:           |             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        |
---------------------------------------+----------------------------------
 The as112 server has too many ERRORs of "Unable to lock logger lockfile":
 {{{
 2012-12-19 21:06:32.312 ERROR [b10-auth.auth/94095] Unable to lock logger
 lockfile
 2012-12-19 21:41:23.189 ERROR [b10-auth.auth/95422] Unable to lock logger
 lockfile
 2012-12-19 21:41:23.266 ERROR [b10-auth.auth/95428] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.cc/63076] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.cc/63076] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.cc/63076] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.cc/63076] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.cc/63076] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.cc/63076] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.490 ERROR [b10-auth.server_common/63076] Unable to
 lock logger lockfile
 2013-02-13 23:07:16.504 ERROR [b10-auth.auth/63078] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.504 ERROR [b10-auth.auth/63079] Unable to lock logger
 lockfile
 2013-02-13 23:07:16.505 ERROR [b10-auth.auth/63075] Unable to lock logger
 lockfile
 2013-02-14 21:48:20.046 ERROR [b10-auth.auth/55135] Unable to lock logger
 lockfile
 2013-02-15 14:36:33.432 ERROR [b10-auth.auth/91220] Unable to lock logger
 lockfile
 2013-02-21 13:50:33.346 ERROR [b10-auth.auth/39545] Unable to lock logger
 lockfile
 }}}

 This happens during startup. The server has multiple b10-auth components.

 Notice it does not have a corresponding message ID so I can't quickly read
 explanation.

 Does it give up too soon?

 Does this message mean I lost another log message?

 How can it log this message if it can't lock the file?

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