[Replying with mailing list address in recipients.] Thank you, Rainer, for quick answer.
On Wed, Feb 12, 2020 at 3:31 PM Rainer Gerhards <[email protected]> wrote: > El mié., 12 feb. 2020 a las 15:26, Peter Viskup via rsyslog > (<[email protected]>) escribió: > > > > In other case it seems those internal rsyslog messages are duplicite > (once > > logged with full syslog-tag with PID and secondly with msg only). Is > there > > some way to supress duplicite logging of these messages? > > May this be config induced? If not, a debug log would be useful. > There are instances in chroot having disabled processing of internal messages (they should log to /dev/log inside the chroot - and they definitely do). ~# cat /chroot/lin/etc/rsyslog.d/global/01-global.conf global(workDirectory="/var/spool/rsyslog") global(action.reportSuspensionContinuation="on") global(processInternalMessages="off") global(abortOnUncleanConfig="on") $EscapeControlCharactersOnReceive off And the standard operating system instance running on the host is reading the /dev/log sockets in chroots: ~# cat /etc/rsyslog.d/chroot-lin-imuxsock.conf input(type="imuxsock" Socket="/chroot/lin/dev/log" CreatePath="on") Do not see any other configuration options related to that message processing. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
