[syslog-ng] Truncated Messages when using templates

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Thu Aug 24 18:28:10 CEST 2006


On Wed, 23 Aug 2006 15:33:40 CDT, Ivan Stegic said:

> We are running syslog-ng 1.6.11-1 on a Fedora 5 Intel Xeon box. We have
> an application specific template that we are logging information for
> into a MySQL 5.0.22 database. If we ever try to log a message that is
> more than 10674 characters in length, the message is truncated. We
> expect to only log this large sized message when the DEBUG level of our
> application is switched to EXTREMELY_HIGH. Now, although this probably
> won't happen often, it will be at that point that we would most need
> that information! If the message is logged to a file, the truncation
> does NOT occur. Does anyone have any insight into this? I would
> appreciate a push in the right direction for more information, or maybe
> even a patch of some sort?


This sounds suspiciously like MySQL isn't allowing an insert with a field that's
more than 10674 characters long.  Have you hand-tested with a throw-away app
(a 5-line Perl for instance) that in fact it's possible to insert longer strings
into the MySQL table?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.balabit.hu/pipermail/syslog-ng/attachments/20060824/4cdb3360/attachment.pgp


More information about the syslog-ng mailing list