[syslog-ng] [Bug 34] New: After sighup master doe not write to logs, but clients think the server is writing to the logs

[bugzilla at bugzilla.balabit.com]

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

           Summary: After sighup master doe not write to logs, but clients
                    think the server is writing to the logs
           Product: syslog-ng
           Version: 2.1.x
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: michael at crowdscience.com
         QAContact: michael at crowdscience.com
Type of the Report: ---
   Estimated Hours: 0.0


We encountered a problem when a sighup is sent to syslo-ng as part of our process to rotate the log file on the syslog-ng master. After the signal is sent and
the log file has been rotated syslog-ng creates a new log file, but does not write to it. During this time the syslog-ng clients think that the master is up
and continue to send their messages to the server (ie not queuing the messages locally). This resulted in a period of time where messages where not logged and
required a stop and start of the syslog-ng service to get the messages logging again. 


The server is running Solaris Nevada snv_67 X86.


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