| 1 |
On Tue, 17 February 2015, at 6:26 pm, lee <lee@××××××××.de> wrote: |
| 2 |
> |
| 3 |
> The log file seem to be some sort of binary that doesn't display too |
| 4 |
> well in less, and there doesn't seem to be any way to read them. |
| 5 |
|
| 6 |
I believe this may be bug 406623. |
| 7 |
|
| 8 |
https://bugs.gentoo.org/show_bug.cgi?id=406623 |
| 9 |
|
| 10 |
Note comment #2 - the "binary zero characters" are not visible with every editor, but if I recollect I was able to see them and delete them when I opened the log files in vim. I think they displayed as "@^" in vim. |
| 11 |
|
| 12 |
Once you know where to look, you can also identify the binary characters using `hexdump -C /var/log/messages`. |
| 13 |
|
| 14 |
I am now running app-admin/syslog-ng-3.4.8 and have threading enabled and the problem is now no longer occurring. |
| 15 |
|
| 16 |
You can establish whether you're affected by 406623 simply by deleting the character(s) (renaming the log file would probably work, too) and rebooting the system. My experience was that the text logfile is "turned to binary" on reboot - the binary characters were logged as part of the kernel's startup messages. This was repeatable and predictable. |
| 17 |
|
| 18 |
Stroller. |
Archives