[syslog-ng]Urgent: Mangled messages in pipe() destinations in version 1.5.19

Balazs Scheidler bazsi@balabit.hu
Fri, 27 Sep 2002 16:26:59 +0200

On Fri, Sep 27, 2002 at 02:47:25PM +0200, Carlos Inacio wrote:
> On Fri, Aug 02, 2002 at 05:26:25PM +0200, Andreas Schulze wrote:
> Hi all,
> We are seeing exactly the same behaviour Andreas described. Actually
> it works fine until version 1.5.8, but if we use any version >1.5.8,
> including patched 1.5.19 and 1.5.20, we get lots of mangled messages.
> So it's not really the same problem that was fixed in 1.5.20.
> Any ideas? We'd also love to use the latest version and not have to stick
> to 1.5.8.
> Thanks in advance,

Without being able to reproduce the bug I _need_ more information. I've
checked out the difference between 1.5.20 and 1.5.8 at the time I received
the original bug report, but saw no reasons that could cause this problem.

What I'd need:
1) the least complex config file that shows the problem
2) strace dump of syslog-ng while receiving this message (only the relevant
parts are needed, e.g. the place where syslog-ng receives this message)

I suspect syslog-ng gets data fragmented in some way, but as I checked the
trivial cases I don't know the real cause.

Thanks in advance,

PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1