Public bug reported:
Description: Ubuntu 12.04 LTS
Release: 12.04
Package: syslog-ng
Version: 3.3.4.dfsg-2ubuntu1
Having syslog-ng configured with mongodb as a destination, I happened to
encounter deadlocks where syslog-ng would stop to process any messages.
The impact is quite severe, as almost all applications which write to
/dev/log will block indefinitely, making the system completely unusable.
Going through the fixes which had been commited since the version
currently in Ubuntu 12.04, I found various fixes concerning mongodb.
There is:
c08618370fc018629d623148452403fb7d0e6f40 afmongodb: Fix a race condition in
the queue & wakeup mechanism
And on the 3.4 branch there is also a fix concerning deadlocks:
d5f78c833a20d3eb5da7372dd70bc79f2f971814 afmongodb: Fix a queue
notify<->wakeup deadlock
Having both of these patches applied, the issue did not reappear. As
these patches only modify code of the mongodb destination module, the
risk of introducing regression for users not deploying that modue is
minimal, while for those that use syslog-ng-mod-mongodb, the patches
help to avoid a very severe problem which, if it occurs, causes denial
of service for most parts of the system. Therefore, I think that these
patches should find their way into LTS.
Also, there are multiple other bugfixes that have been commited since
3.3.4. It might be a good idea to look at those as well.
** Affects: syslog-ng (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049202
Title:
syslog-ng-mod-mongodb has deadlock problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1049202/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
