tags 689025 + moreinfo
thanks
Hi Dominik,
On 28/09/12 01:27 PM, Dominik George wrote:
A full GDB backtrace of all threads would be useful for examining this issue
any further.
kI will have to build a test case for that. Obviously, I cannot break
production deliberately for that ;).
Did you
Package: slapd
Version: 2.4.31-1
Severity: important
The slapd process hangs when sending log data to an unresponsive syslogd.
In out site setup, all servers log to a central MySQL database through rsyslog.
rsyslog becomes unresponsive when having too much data queued, which happened
when
the
--On Friday, September 28, 2012 2:19 PM +0200 Dominik George
n...@naturalnet.de wrote:
Package: slapd
Version: 2.4.31-1
Severity: important
The slapd process hangs when sending log data to an unresponsive syslogd.
In out site setup, all servers log to a central MySQL database through
A full GDB backtrace of all threads would be useful for examining this issue
any further.
kI will have to build a test case for that. Obviously, I cannot break
production deliberately for that ;).
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Quanah Gibson-Mount writes:
n...@naturalnet.de wrote:
Although this is possibly an rsyslog bug,
Yes. Syslog is supposed to be lossy when it can't keep up.
It should log problems, not create them without logging them.
Imagine you had a lossy syslog but a non-lossy openlog() option: If
the log
5 matches
Mail list logo
