BIND 10 #1629: logging with garbage in it
BIND 10 Development
do-not-reply at isc.org
Fri Jun 15 09:56:58 UTC 2012
#1629: logging with garbage in it
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: UnAssigned
Type: | Status: assigned
defect | Milestone:
Priority: | Sprint-20120619
medium | Resolution:
Component: | Sensitive: 0
logging | Sub-Project: DNS
Keywords: | Estimated Difficulty: 8
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by stephen):
Replying to [comment:11 jinmei]:
> Replying to [comment:10 jreed]:
> > Saw this again, but was in the trac1818 branch:
> >
> > {{{
> > 2012-04-12 04:56:02.931 DEBUG [b10-auth.cc] CC_ESTABLISHED
successfully connected to message queue daemon
> > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ DEBUG
[b10-auth.datasrc] DATASRC_CACHE_CREATE creating the hotspot cache
> > }}}
Probably stating the obvious, but the !^@ characters are in the position
where the date and time should be. Also, there are 23 of them, which is
the same number of characters in the "YYYY-MM-DD HH:MM:SS.sss" format we
use. This pattern also occurs in comment:10 and comment:3. As the date
and time are generated within log4cplus, this does seem to suggest that
the problem lies there.
Other examples are different (although the first corrupted line in the
example giving in the description of this ticket contains 23 consecutive
!^@ characters), but some of these may be due to the problem we've had
with multiple processes getting their logging output mixed up.
--
Ticket URL: <http://bind10.isc.org/ticket/1629#comment:17>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list