[Twisted-Python] Garbage in logfiles?

Tom Prince tom.prince at ualberta.net
Wed Oct 16 16:07:29 MDT 2013


Conor Sayres <sayresc at gmail.com> writes:

> I have set up twisted logging to record all communication between our devices.  When we simulate our system with a high frequency log rollover rate (~5 seconds), many of the logs contain only garbage.  Here is an example of a few lines in a given bad log file:
>
> 3230 3133 2d31 302d 3136 2031 303a 3131
> 3a34 352d 3037 3030 205b 2d5d 2044 6576
> 436d 6428 5354 4154 5553 290a 3230 3133
> 2d31 302d 3136 2031 303a 3131 3a34 352d
> 3037 3030 205b 2d5d 2044 6576 436d 6428
> 5354 4154 5553 290a 3230 3133 2d31 302d

How are you viewing the log file? I suspect
you are using less, and that the file contains
some control characters, and less is automatically
showing you a hex dump. Try using `less -A`.

The above lines when coverted from hex are:

2013-10-16 10:11:45-0700 [-] DevCmd(STATUS)
2013-10-16 10:11:45-0700 [-] DevCmd(STATUS)
2013-10

which looks like part of a log file.

  Tom



More information about the Twisted-Python mailing list