If your lines are long, you might be running up against the line length limit. You might do something like the following in options: # maximum length of message in bytes # this is only limited by the program listening on the /dev/log Unix # socket, glibc can handle arbitrary length log messages, but -- for # example -- syslogd accepts only 1024 bytes # (default is 2048) log_msg_size(8192); And see if that helps. ________________________________________ From: syslog-ng-bounces@lists.balabit.hu [syslog-ng-bounces@lists.balabit.hu] On Behalf Of Ian Lesperance [ianl@ezpublishing.com] Sent: Wednesday, December 01, 2010 2:28 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Extra Lines Truncated That makes sense, and it'd be great if that's what it did, but it actually seems to just drop the rest of the message entirely. The extra lines don't show up anywhere in the log file, with or without metadata. Based on the search results I found on Google, I thought syslog-ng replaced newlines with spaces just like syslog. So that's no longer the case? I'd ask what version it was changed in, but I'm not seeing either behavior, so I doubt that's the issue. Ian