Hello there, On Thu, Mar 07, 2013 at 01:07:38PM +0100, Tomas Pospisek wrote: > On Thu, 7 Mar 2013, Michael Biebl wrote: > > >Is that on virtualised hardware? > > No, that's on the metal. However each lxc container is *also* > running out of the box rsyslog (without any config adaptations), so > it might be that there's a problem there somewhere with all those > rsyslogs getting along. However of course each syslog is sitting on > its own FS and thus on its own log files. > > Ad hoc I couldn't tell what access rights those lxc containers have > wrt to the kernel log feed and how that feed works.
FWIW, I experienced the same messed-up logs some time ago when running rsyslog in an LXC guest. I circumvented that by disabling kernel logging support in the guest as follows: diff --git a/rsyslog.conf b/rsyslog.conf index 2a7f9f9..94fff07 100644 --- a/rsyslog.conf +++ b/rsyslog.conf @@ -9,7 +9,7 @@ ################# $ModLoad imuxsock # provides support for local system logging -$ModLoad imklog # provides kernel logging support (previously done by rklogd) +#$ModLoad imklog # provides kernel logging support (previously done by rklogd) #$ModLoad immark # provides --MARK-- message capability # provides UDP syslog reception Cheers, Flo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
