From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D4D3D138A1A for ; Tue, 17 Feb 2015 23:55:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 40066E08D6; Tue, 17 Feb 2015 23:54:57 +0000 (UTC) Received: from smarthost01b.mail.zen.net.uk (smarthost01b.mail.zen.net.uk [212.23.1.3]) by pigeon.gentoo.org (Postfix) with ESMTP id 09FC3E082F for ; Tue, 17 Feb 2015 23:54:55 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01b.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YNryh-00008n-90 for gentoo-user@lists.gentoo.org; Tue, 17 Feb 2015 23:54:55 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] syslog-ng: how to read the log files Date: Tue, 17 Feb 2015 23:54:54 +0000 Message-ID: <2933343.qtGMBbSiIJ@wstn> Organization: Society for Retired Gentlefolk User-Agent: KMail/4.14.3 (Linux/3.17.8-gentoo-r1; KDE/4.14.3; x86_64; ; ) In-Reply-To: References: <5053257.RtBGZSofvK@wstn> <4611964.hfD2vZR9R2@wstn> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01b-IP: [82.69.80.10] X-Archives-Salt: 6cc212b3-b833-46a1-9af9-a91eb6a205e7 X-Archives-Hash: ced0218d244412d88b98970940694864 On Wednesday 18 February 2015 00:23:19 Jan Sever wrote: > On 02/18/2015 12:13 AM, Peter Humphrey wrote: > > On Tuesday 17 February 2015 22:51:55 Peter Humphrey wrote: > >> On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: > >>>> On Feb 17, 2015, at 20:26, lee wrote: > >>>> how do you read the log files when using syslog-ng? > >>>> The log file seem to be some sort of binary that doesn't display > >>>> too > >>>> well in less, and there doesn't seem to be any way to read them. > >>> > >>> This was discussed earlier on this list... Actually what syslog-ng > >>> produces is plain text. There seemed to be a bug that creates some > >>> binary (i.e. unreadable characters) and that causes less to > >>> consider > >>> files to be binary and show them incorrectly. > >> > >> Yes, that was me. I found that something had marked > >> /var/log/messages > >> as a binary file. There's nothing in it that can't be read, no > >> mysterious characters or anything; it's just marked as binary. All > >> you have to do is to move it, then cat it back into place. I did > >> that > >> with no ill effects. > > > > Actually, this is what I did, as I reported here on 26/12: > >> 1. Boot rescue system and mount main system > >> 2. # cd /mnt/main/var/log > >> 3. # mv messages messages.bin > >> 4. # strings messages.bin > messages > >> 5. # rm messages.bin > >> 6. Reboot. > > When I had similar problem, I changed threaded(yes) to threaded(no) > in syslog-ng.conf and the problem disappeared. Maybe it helps you too. Good idea. Sounds like a bug report is needed, unless it's already been superseded. -- Rgds Peter.