[syslog-ng] [Bug 270] New: deadlock with patterndb and format-json ( debug NOT enabled in compilation)

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=270

           Summary: deadlock with patterndb and format-json (debug NOT
                    enabled in compilation)
           Product: syslog-ng
           Version: 3.5.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: bugzilla.balabit at faxm0dem.org
Type of the Report: bug
   Estimated Hours: 0.0


Created an attachment (id=90)
 --> (https://bugzilla.balabit.com/attachment.cgi?id=90)
syslog-ng configuration and patterndb file

This one was hard to isolate.
Using the minimal attached configuration, it's very easy to lock the system down by running the following command (bourne shell):

$ i=0; while echo 'sshd: Received disconnect from 1.2.3.4: 11: disconnected by user' > /var/tmp/syslo
g-ng.src.fifo; do printf .$i.; i=$(($i+1)); done
.0..1..2..3..4..5..6..7..8..9..10..11..12..13..14..15..16..17..18..19..20..21..22..23..24..25..26..27..28
[...]
124..125
[DEADLOCK]

After that, syslog-ng is completely locked.
command used to run syslog-ng:

/sbin/syslog-ng -f /home/faxm0dem/syslog-ng-bug/syslog-ng.conf -R /tmp/syslog-ng.persist -p /tmp/syslog-ng.pid

Most importantly, this does *only* happen when --enable-debug is *not* switched during compilation.
Moreover, an example pattern in the provided patterndb shows how this can be avoided by renaming the variables.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.