[syslog-ng] reloading (HUP) syslog-ng -> mutilation of messages in mongodb

[Gergely Nagy]

"Lucas, Sascha" <Sascha.Lucas at gisa.de> writes:

> Hi,
>
> after reloading syslog-ng 3.4.1 (SIGHUP) I have random issues with
> mutilation of messages to a mongodb destination. Sometimes the value of
> the MESSAGE key is just truncated. An other time i.e. LEGACY_MSGHDR,
> MESSAGE, PROGRAM are empty and the HOST value is mutilated. And
> sometimes syslog-ng stops inserting into mongodb.
>
> Any hints on this?

Hrm. Haven't experienced anything like that yet... do you happen to have
file sources? Or the stuff that gets corrupted is coming from the
network?

Are there any errors in the internal log, any cores perhaps?

-- 
|8]