[syslog-ng] deadlock when logging to SQL destination (PostgreSQL)

[Tomáš Novosad]

Hello,

in fact, i've experienced that flow-control problem earlier.
I've disabled flow-control, but after some time this "deadlock"
problem appeared.

I will reporoduce the problem and will provide as much info as You'll
need. Do You want me to post the data here on mailing list, or should i
open a bug report somewhere (balabit website)?

Thanks for help
-- 
Tomáš Novosad
LinuxBox.cz, s.r.o.
28. října 168, 709 00 Ostrava

tel.:   +420 591 166 221
mobil:  +420 737 238 655
email:  tomas.novosad at linuxbox.cz
jabber: novosad at linuxbox.cz
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis at linuxbox.cz

On  5. 1. 12:11, Scheidler, Balázs wrote:
> Hi,
> 
> checking the backtrace again, it might actually be a genuine deadlock. can
> you give a backtrace of all the threads as syslog-ng stalls like that?
> 
> 
> -- 
> Bazsi
> 
> On Mon, Jan 5, 2015 at 12:09 PM, Scheidler, Balázs <
> balazs.scheidler at balabit.com> wrote:
> 
> > Hi,
> >
> > You probably have flow-control enabled, in which case if the destination
> > stalls, syslog-ng will stop reading its inputs as well. Workarounds:
> >
> > 1) increase the window-size (log-iw-size at the source) & destination
> > buffer size (log-fifo-size option at the destination), this will let more
> > leeway, until syslog-ng blocks if its destination blocks
> > 2) have postgres log to a file, and then read that file as a file source.
> > 3) last, but not least disable flow-control
> >
> > Hope this helps,
> >
> >
>