1 |
On 02/18/2015 12:13 AM, Peter Humphrey wrote: |
2 |
> On Tuesday 17 February 2015 22:51:55 Peter Humphrey wrote: |
3 |
>> On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: |
4 |
>>>> On Feb 17, 2015, at 20:26, lee <lee@××××××××.de> wrote: |
5 |
>>>> how do you read the log files when using syslog-ng? |
6 |
>>>> The log file seem to be some sort of binary that doesn't display |
7 |
>>>> too |
8 |
>>>> well in less, and there doesn't seem to be any way to read them. |
9 |
>>> |
10 |
>>> This was discussed earlier on this list... Actually what syslog-ng |
11 |
>>> produces is plain text. There seemed to be a bug that creates some |
12 |
>>> binary (i.e. unreadable characters) and that causes less to consider |
13 |
>>> files to be binary and show them incorrectly. |
14 |
>> |
15 |
>> Yes, that was me. I found that something had marked /var/log/messages |
16 |
>> as a binary file. There's nothing in it that can't be read, no |
17 |
>> mysterious characters or anything; it's just marked as binary. All |
18 |
>> you have to do is to move it, then cat it back into place. I did that |
19 |
>> with no ill effects. |
20 |
> |
21 |
> Actually, this is what I did, as I reported here on 26/12: |
22 |
> |
23 |
>> 1. Boot rescue system and mount main system |
24 |
>> 2. # cd /mnt/main/var/log |
25 |
>> 3. # mv messages messages.bin |
26 |
>> 4. # strings messages.bin > messages |
27 |
>> 5. # rm messages.bin |
28 |
>> 6. Reboot. |
29 |
> |
30 |
|
31 |
When I had similar problem, I changed threaded(yes) to threaded(no) |
32 |
in syslog-ng.conf and the problem disappeared. Maybe it helps you too. |
33 |
|
34 |
-- |
35 |
Jan Sever |