Am 15.09.2014 um 14:23 schrieb Umut Tezduyar Lindskog: > On Mon, Sep 15, 2014 at 1:38 PM, David Herrmann <dh.herrm...@gmail.com> wrote: >> Hi >> >> On Mon, Sep 15, 2014 at 1:20 PM, Reindl Harald <h.rei...@thelounge.net> >> wrote: >>> anybody an idea why? >> >> The syslog daemon couldn't keep up with reading the log-messages. You >> might wanna increase the syslog receive-queue in your syslog daemon or >> make sure you don't flush that many messages to it. > You might want to take a look at the following thread too just to > increase the syslog limit: > http://lists.freedesktop.org/archives/systemd-devel/2014-August/021897.html
>> My workaround is adding SendBuffer=8M to >> systemd-journald-dev-log.socket well, there is already "ReceiveBuffer=8M" and using only the settings below as far as i understand is a pull from rsyslog and not a forward since without "$IMJournalStateFile" every time you restart rsyslog you got the same old log repeated $ModLoad imjournal $MainMsgQueueSize 30000 $WorkDirectory /var/lib/rsyslog $IMJournalStateFile imjournal.state _______________________________________________________ [Unit] Description=Journal Socket Documentation=man:systemd-journald.service(8) man:journald.conf(5) DefaultDependencies=no Before=sockets.target # Mount and swap units need this. If this socket unit is removed by an # isolate request the mount and swap units would be removed too, # hence let's exclude this from isolate requests. IgnoreOnIsolate=yes [Socket] ListenStream=/run/systemd/journal/stdout ListenDatagram=/run/systemd/journal/socket ListenDatagram=/dev/log SocketMode=0666 PassCredentials=yes PassSecurity=yes ReceiveBuffer=8M
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
