1 |
On Tuesday 17 Feb 2015 23:13:08 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 |
> > 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 |
How often do you have to do this? |
30 |
|
31 |
-- |
32 |
Regards, |
33 |
Mick |