[syslog-ng] [Bug 82] New: Buffered messages are lost on SIGHUP signal

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Tue May 11 17:12:40 CEST 2010


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

           Summary: Buffered messages are lost on SIGHUP signal
           Product: syslog-ng
           Version: 2.0.x
          Platform: PC
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: urbestfriend at gmail.com
Type of the Report: ---
   Estimated Hours: 0.0


I'm using version 2.0.10 syslog-ng version.

I ran a simple test with 

filter f_myprog       { program(zpem); };

destination my_dest { unix-stream("/dev/mylog" template("$MSGONLY\n") template_escape(no) log_fifo_size(1000) );  }; 

log { source(src); filter(f_myprog); destination(my_dest); };

When destination is not available ( server is stopped)  and if I issue SIGHUP signal , all buffered messages are lost and I dont receive any messages when
destination comes back online
But if I dont issue SIGHUP when destination is down , it works well and I'm able to receive messages when destination comes up.Ideally with log_fifo_size(), I
would expect 
the messages to be buffered across reloads, but this is not the case in the version which I am using.


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


More information about the syslog-ng mailing list