Package: rsyslog Version: 5.8.11-1+b1 Severity: important We recently added the omysql backend to rsyslog to centralize all logging to a MySQL database. The link to the database was a bit flakey lately and a syslog client, slapd, was producing tons of log lines for debugging purposes. This lead to rsyslog staying behind with logging for nearly 30 minutes and apparently filling up all its buffers. That prevented rsyslog from accepting more logs, which even froze slapd (which is a bug in slapd as well, see #689025).
rsyslog should rather drop messages to a certain backend if it is not available and keep on logging to available backends or at least make this behaviour configurable so a broken logging backend can not freeze rsyslog. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rsyslog depends on: ii initscripts 2.88dsf-32 ii libc6 2.13-35 ii lsb-base 4.1+Debian7 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages rsyslog recommends: ii logrotate 3.8.1-4 Versions of packages rsyslog suggests: pn rsyslog-doc <none> pn rsyslog-gnutls <none> pn rsyslog-gssapi <none> ii rsyslog-mysql 5.8.11-1+b1 pn rsyslog-relp <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
