https://bugzilla.balabit.com/show_bug.cgi?id=9 Summary: syslog-ng crashes when /etc/eventlog.conf exists Product: syslog-ng Version: 2.0.x Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447105 OS/Version: Linux Status: NEW Severity: major Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: sasa@debian.org Type of the Report: bug Estimated Hours: 0.0
From bugs.debian.org:
When /etc/eventlog.conf exists and contains "[hello]" (for example), syslog-ng segfaults at start. Here is the end of strace output: uname({sys="Linux", node="naruto", ...}) = 0 brk(0) = 0x8088000 brk(0x80a9000) = 0x80a9000 open("/etc/localtime", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=1082, ...}) = 0 fstat64(3, {st_mode=S_IFREG|0644, st_size=1082, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f7c000 read(3, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\f\0\0\0\f\0"..., 4096) = 1082 close(3) = 0 munmap(0xb7f7c000, 4096) = 0 rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0 rt_sigaction(SIGHUP, {0x804aae0, [], 0}, NULL, 8) = 0 rt_sigaction(SIGTERM, {0x804aaf0, [], 0}, NULL, 8) = 0 rt_sigaction(SIGINT, {0x804aaf0, [], 0}, NULL, 8) = 0 rt_sigaction(SIGCHLD, {0x804ab00, [], 0}, NULL, 8) = 0 rt_sigaction(SIGSEGV, {0x804ab10, [], SA_ONESHOT}, NULL, 8) = 0 gettimeofday({1192688001, 803861}, NULL) = 0 open("/etc/eventlog.conf", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=8, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f7c000 read(3, "[hello]\n", 4096) = 8 --- SIGSEGV (Segmentation fault) @ 0 (0) --- kill(12421, SIGSEGV) = 0 sigreturn() = ? (mask now []) --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ Process 12421 detached I did not find any documentation about /etc/eventlog.conf file. I have found this bug because such file was created by an unrelated application. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.