3.4 on opensuse factory
Hello, When trying to run syslog-ng 3.4 on openSUSE factory, the supervisor process starts, but it's child segfaults continuously. I tried to revert the big nvtable patch, which solved my problem previously, but it did not help. Here are two backtraces, practically the same: With the nvtable patch: (gdb) bt #0 0x00007f3e447516c6 in __memcpy_ssse3_back () from /lib64/libc.so.6 #1 0x00007f3e44f1a3ff in nv_table_add_value () from /lib64/libsyslog-ng-3.4.0alpha1.so #2 0x00007f3e44f0858f in log_msg_set_value () from /lib64/libsyslog-ng-3.4.0alpha1.so #3 0x00007f3e44f015db in log_src_driver_queue_method () from /lib64/libsyslog-ng-3.4.0alpha1.so #4 0x00007f3e44f12bfe in log_source_queue () from /lib64/libsyslog-ng-3.4.0alpha1.so #5 0x00007f3e44efa008 in afinter_source_post () from /lib64/libsyslog-ng-3.4.0alpha1.so #6 0x00007f3e44f338d4 in iv_event_run_pending_events () from /lib64/libsyslog-ng-3.4.0alpha1.so #7 0x00007f3e44f33c49 in iv_event_raw_got_event () from /lib64/libsyslog-ng-3.4.0alpha1.so #8 0x00007f3e44f3534a in iv_main () from /lib64/libsyslog-ng-3.4.0alpha1.so #9 0x00007f3e44f18532 in main_loop_run () from /lib64/libsyslog-ng-3.4.0alpha1.so #10 0x00000000004016e1 in main () With the nvtable patch (https://github.com/bazsi/syslog-ng-3.4/commit/1c3a37764d98d5a37f2cd3c79f7f40...) reverted: (gdb) bt #0 0x00007f6fdb8b86c6 in __memcpy_ssse3_back () from /lib64/libc.so.6 #1 0x00007f6fdc0818bf in nv_table_add_value () from /lib64/libsyslog-ng-3.4.0alpha1.so #2 0x00007f6fdc06f620 in log_msg_set_value () from /lib64/libsyslog-ng-3.4.0alpha1.so #3 0x00007f6fdc0685cb in log_src_driver_queue_method () from /lib64/libsyslog-ng-3.4.0alpha1.so #4 0x00007f6fdc079dbe in log_source_queue () from /lib64/libsyslog-ng-3.4.0alpha1.so #5 0x00007f6fdc060ff8 in afinter_source_post () from /lib64/libsyslog-ng-3.4.0alpha1.so #6 0x00007f6fdc09afc4 in iv_event_run_pending_events () from /lib64/libsyslog-ng-3.4.0alpha1.so #7 0x00007f6fdc09b339 in iv_event_raw_got_event () from /lib64/libsyslog-ng-3.4.0alpha1.so #8 0x00007f6fdc09ca3a in iv_main () from /lib64/libsyslog-ng-3.4.0alpha1.so #9 0x00007f6fdc07f942 in main_loop_run () from /lib64/libsyslog-ng-3.4.0alpha1.so #10 0x00000000004016e1 in main () Is it something in syslog-ng, or I should rather report it at openSUSE? Bye, -- Peter Czanik (CzP)<czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/
Peter Czanik <czanik@balabit.hu> writes:
Hello,
When trying to run syslog-ng 3.4 on openSUSE factory, the supervisor process starts, but it's child segfaults continuously. I tried to revert the big nvtable patch, which solved my problem previously, but it did not help.
It's not the nvtable patch that causes problems. I posted a patch here earlier that fixes the issue, but it hasn't been pulled into 3.4 yet (it was, Bazsi just didn't push his tree out, it seems). The patch itself is available on my sandbox/3.4 branch, in this commit: https://github.com/algernon/syslog-ng/commit/05e4e594e1fda8d91188196365fdc30...
Is it something in syslog-ng, or I should rather report it at openSUSE?
It's a syslog-ng 3.4 bug, patch above :) -- |8]
On 04/20/2012 04:45 PM, Gergely Nagy wrote:
Peter Czanik<czanik@balabit.hu> writes:
Hello,
When trying to run syslog-ng 3.4 on openSUSE factory, the supervisor process starts, but it's child segfaults continuously. I tried to revert the big nvtable patch, which solved my problem previously, but it did not help. It's not the nvtable patch that causes problems. I posted a patch here earlier that fixes the issue, but it hasn't been pulled into 3.4 yet (it was, Bazsi just didn't push his tree out, it seems).
The patch itself is available on my sandbox/3.4 branch, in this commit: https://github.com/algernon/syslog-ng/commit/05e4e594e1fda8d91188196365fdc30...
Is it something in syslog-ng, or I should rather report it at openSUSE? It's a syslog-ng 3.4 bug, patch above :)
And it fixed my problem! Thanks! Bye, -- Peter Czanik (CzP)<czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/
The patch is already available on my trees and in 3.4.0alpha2. Sorry for the confusion. On Sat, 2012-04-21 at 15:53 +0200, Peter Czanik wrote:
On 04/20/2012 04:45 PM, Gergely Nagy wrote:
Peter Czanik<czanik@balabit.hu> writes:
Hello,
When trying to run syslog-ng 3.4 on openSUSE factory, the supervisor process starts, but it's child segfaults continuously. I tried to revert the big nvtable patch, which solved my problem previously, but it did not help. It's not the nvtable patch that causes problems. I posted a patch here earlier that fixes the issue, but it hasn't been pulled into 3.4 yet (it was, Bazsi just didn't push his tree out, it seems).
The patch itself is available on my sandbox/3.4 branch, in this commit: https://github.com/algernon/syslog-ng/commit/05e4e594e1fda8d91188196365fdc30...
Is it something in syslog-ng, or I should rather report it at openSUSE? It's a syslog-ng 3.4 bug, patch above :)
And it fixed my problem! Thanks! Bye,
-- Bazsi
participants (3)
-
Balazs Scheidler
-
Gergely Nagy
-
Peter Czanik