[syslog-ng] [Bug 260] New: exit with code 134

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Thu Nov 7 03:15:39 CET 2013


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

           Summary: exit with code 134
           Product: syslog-ng
           Version: 3.4.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: erempel at uvic.ca
Type of the Report: ---
   Estimated Hours: 0.0


I just did a reload on version 3.4.4 (with latest patches) and triggered

2013-11-05T21:24:33-08:00 host daemon.crit supervise/syslog-ng[25895]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'

Is it possible that the return code of syslog-ng is somehow linked to the return code of a child program destination?

core file sent to Balazs in private e-mail


-- 
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