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 EA7DF138A87 for ; Mon, 23 Feb 2015 17:49:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CFBACE0851; Mon, 23 Feb 2015 17:49:12 +0000 (UTC) Received: from mail0200.smtp25.com (mail0200.smtp25.com [174.37.170.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AC4F1E0835 for ; Mon, 23 Feb 2015 17:49:11 +0000 (UTC) Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id t1NHn9I5004134 for ; Mon, 23 Feb 2015 12:49:09 -0500 From: covici@ccs.covici.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] syslog-ng: how to read the log files In-reply-to: References: <87lhjws8ci.fsf@heimdali.yagibdah.de> <28267.1424201355@ccs.covici.com> <87d257q7en.fsf@heimdali.yagibdah.de> <20150218223115.7fb56f66@digimed.co.uk> <87vbitldj5.fsf@heimdali.yagibdah.de> <20150223091529.656c0008@marcec.fritz.box> <16447.1424680874@ccs.covici.com> Comments: In-reply-to =?us-ascii?Q?=3D=3FUTF-8=3FB=3FQ2FuZWsgUGVsw6FleiBWY?= =?us-ascii?Q?Wxkw6lz=3F=3D?= message dated "Mon, 23 Feb 2015 10:18:14 -0600." X-Mailer: MH-E 8.5; nmh 1.6; GNU Emacs 23.4.1 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-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Mon, 23 Feb 2015 12:49:09 -0500 Message-ID: <4133.1424713749@ccs.covici.com> X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: s-out-001.smtp25.com-t1NHn9Oi025245 X-Archives-Salt: 13722e3d-889b-4a4c-9f97-fbfc54c97886 X-Archives-Hash: 3e1373e3293e4e209fa3bc1068aefc36 Canek Pel=C3=A1ez Vald=C3=A9s wrote: > On Mon, Feb 23, 2015 at 3:41 AM, wrote: > > > > Marc Joliet wrote: > > > > > Am Mon, 23 Feb 2015 00:41:50 +0100 > > > schrieb lee : > > > > > > > Neil Bothwick writes: > > > > > > > > > On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: > > > > > > > > > >> > I wonder if the OP is using systemd and trying to read the > journal > > > > >> > files? > > > > >> > > > > >> Nooo, I hate systemd ... > > > > >> > > > > >> What good are log files you can't read? > > > > > > > > > > You can't read syslog-ng log files without some reading software, > usually > > > > > a combination of cat, grep and less. systemd does it all with > journalctl. > > > > > > > > > > There are good reasons to not use systemd, this isn't one of them. > > > > > > > > To me it is one of the good reasons, and an important one. Plain t= ext > > > > can usually always be read without further ado, be it from rescue > > > > systems you booted or with software available on different operating > > > > systems. It can be also be processed with scripts and sent as emai= l. > > > > You can probably even read it on your cell phone. You can still re= ad > > > > log files that were created 20 years ago when they are plain text. > > > > > > > > Can you do all that with the binary files created by systemd? I ca= n't > > > > even read them on a working system. > > > > > > What Canek and Rich already said is good, but I'll just add this: it's > not like > > > you can't run a classic syslog implementation alongside the systemd > journal. > > > On my systems, by *default*, syslog-ng kept working as usual, getting > the logs > > > from the systemd journal. If you want to go further, you can even > configure > > > the journal to not store logs permanently, so that you *only* end up > with > > > plain-text logs on your system (Duncan on gentoo-amd64 went this way). > > > > > > So no, the format that the systemd journal uses is most decidedly *no= t* > a reason > > > against using systemd. > > > > > > Personally, I'm probably going to uninstall syslog-ng, because > journalctl is > > > *such* a nice way to read logs, so why run something whose output I'll > never > > > read again? I recommend reading > > > http://0pointer.net/blog/projects/journalctl.html for examples of the > kind of > > > stuff you can do that would be cumbersome, if not *impossible* with > regular > > > syslog. > > > > Except that I get lots of messages about the system journal missing > > messages when forwarding to syslog, so how can I make sure this does not > > happening? >=20 > Could you please show those messages? systemd sends *everything* to the > journal, and then the journal (optionally) can send it too to a regular > syslog. In that sense, it's impossible for the journal to miss any messag= e. >=20 > The only way in which the journal could miss messages is at very early bo= ot > stages; but with a proper initramfs (like the ones generated with dracut), > even those get caught. You get to put an instance of systemd and the > journal inside the initramfs, and so it's available almost from the > beginning. >=20 > And if you use gummiboot, then you can even log from the moment the UEFI > firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. --=20 Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com