Alexandre Biancalana <biancalana@gmail.com> writes:
On Fri, Oct 18, 2013 at 6:01 AM, Balazs Scheidler <bazsi77@gmail.com> wrote:
I remember a bug in that caused similar symptoms when the output template produced zero length strings.
That has been fixed though. But can you try that regardless?
Can you perhaps use gdb to check where it is spinning?
If not, I would need to reproduce it.
It only happens when I parse log using patterndb mentioned earlier with format_json --scope nv-pairs.
Follow the gdb backtrace, let me know if you need anything else.
Program received signal SIGINT, Interrupt. g_trash_stack_height (name=<value optimized out>, value=0x620d70 "10228", user_data=0x7fffffffe200) at /usr/include/glib-2.0/glib/gutils.h:413 413 i++; (gdb) bt #0 g_trash_stack_height (name=<value optimized out>, value=0x620d70 "10228", user_data=0x7fffffffe200) at /usr/include/glib-2.0/glib/gutils.h:413 #1 vp_walker_name_split (name=<value optimized out>, value=0x620d70 "10228", user_data=0x7fffffffe200) at value-pairs.c:455
Hrm. name would be very useful to have here. Can you perhaps compile syslog-ng with CFLAGS="-ggdb3 -O0", and do a backtrace with that? I'll try to reproduce the problem with the configs you provided too, but I likely won't be able to do that before monday. -- |8]