[syslog-ng] [Bug 139] New: syslog-ng crashes on SIGHUP when rewrite used in multiple log{} declarations

[bugzilla at bugzilla.balabit.com]

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

           Summary: syslog-ng crashes on SIGHUP when rewrite used in
                    multiple log{} declarations
           Product: syslog-ng
           Version: 3.2.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: bugzilla.syslogng at feystorm.net
Type of the Report: ---
   Estimated Hours: 0.0


This is for version 3.3.1 which isnt an available version in the bug tracker.

I've managed to create a situation where syslog-ng crashes when it receives a SIGHUP, and a certain rewrite has been used in at least 3 different log{}
declarations.

Below is the extremely stripped down configuration I've created which duplicates the issue. With the below configuration, when syslog-ng receives a HUP, it
will get a segfault in malloc_consolidate().
Additionally, the process which monitors syslog-ng for crashing doesnt appear to have a signal handler for SIGHUP, so the monitor process will die when it gets
a HUP. This is a problem, at least on redhat as the redhat init script sends a HUP to both the monitor process and the real worker process when the init script
is called with `reload`


@version: 3.3
@include "scl.conf"
source s_local {
   system();
};
rewrite r_fext {
   #set("$LEVEL",value('FEXT'));
   subst('foo','bar', value('FEXT') type('string'));
};
log { source(s_local); rewrite(r_fext); };
log { source(s_local); rewrite(r_fext); };
log { source(s_local); rewrite(r_fext); };


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