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