Then I would guess that whatever method you are using to send the old log files to syslog-ng is stripping the newline characters, making it look like one gigantic message. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Daniel L. Spells Sr. Sent: 29 December 2008 15:59 To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] importing old syslog-ng messages I have pushed that number to 90K, and get the same message, except the "log_msg_size=XXXX" changes to the what ever value the XXXX is set to in the log, and nothing is written the the database. On Mon, December 29, 2008 05:36, Balazs Scheidler wrote:
On Tue, 2008-12-16 at 11:44 -0600, Daniel L. Spells Sr. wrote:
I am getting:
"syslog-ng[18859]: Message length overflow, line is split, log_msg_size=4096"
When I try to cat the log files to the named pipe. It repeats until it completes the lines in the log file.
This is on a base install on a Suse box.
the message above says that you have messages over 4096 bytes in length. increase log_msg_size().
-- Bazsi
_________________________________________________________________________ _____ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html