Here's that part of the conf options { sync (0); time_reopen (10); log_fifo_size (1000); long_hostnames (off); log_msg_size(1048576); use_dns (yes); use_fqdn (no); create_dirs (no); keep_hostname (yes); }; I think we're OK >> I am looking into the previous suggestion that it is related to MySQL... I'll update here as soon as I have more info. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Friday, August 25, 2006 6:56 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Truncated Messages when using templates On Wed, 2006-08-23 at 15:33 -0500, Ivan Stegic wrote:
Hello everyone...
We have chosen syslog-ng for our corporate application's central logging daemon and are very happy with it so far. Just one problem: truncated messages.
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?
Hmm... macro expansion uses the value for log_msg_size() for determining the format buffer size. What is your setting? -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html