RE: [syslog-ng]Possible overflow?
I didn't see if any mailed in a resolution to this problem, I'm still having it. I'm running Solaris 8 (SPARC) w/syslog-ng-1.5.13 and libol-0.3.1. Also, when I run more or less on one of the log files, I occassionally get the error "file may be a binary, continue?"
I too get high ASCII characters, but on a regular basis across multiple systems. I have about 20 hosts logging to two syslog-ng systems. I see this anywhere from a Foundry routers, to Solaris 8, and Lucent Maxes: ..smf-jumpstart A<A0><E1>$<30>Dec 1.. ..smf-modem-01 ^B^D^E<B4><134>ASCEND: slot 2.. ..smf-dist-01 ^B^D^E<B4><14>smf-dist-01, Interface...
Thanks, Nicholas Berry Systems Engineer RagingWire Telecommunications, Inc. 2710 Gateway Oaks Dr., Suite 300 South Sacramento, CA 95833 Phone: 916.286.4048 Fax: 916.921.4148 E-mail: nberry@ragingwire.com www.ragingwire.com -----Original Message----- From: Nicholas Berry Sent: Friday, December 21, 2001 9:20 AM To: syslog-ng@lists.balabit.hu Subject: RE: [syslog-ng]Possible overflow? I too get high ASCII characters, but on a regular basis across multiple systems. I have about 20 hosts logging to two syslog-ng systems. I see this anywhere from a Foundry routers, to Solaris 8, and Lucent Maxes: ..smf-jumpstart A<A0><E1>$<30>Dec 1.. ..smf-modem-01 ^B^D^E<B4><134>ASCEND: slot 2.. ..smf-dist-01 ^B^D^E<B4><14>smf-dist-01, Interface... Thanks, Nicholas Berry Systems Engineer RagingWire Telecommunications, Inc. 2710 Gateway Oaks Dr., Suite 300 South Sacramento, CA 95833 Phone: 916.286.4048 Fax: 916.921.4148 E-mail: nberry@ragingwire.com www.ragingwire.com -----Original Message----- From: Thomas Kaehn [mailto:tk@westend.com] Sent: Friday, December 21, 2001 3:04 AM To: syslog-ng@lists.balabit.hu Subject: [syslog-ng]Possible overflow? Hi, in some logs I discovered an ascii character with the value 181 instead of a newline: ... D4-RIPE|<181>Dec 20 19:02 ... Unfortunately I can't reproduce this error. But maybe it's a known error? It occured when logging whole mails to syslog. Does anyone know a possible cause? Ciao, Thomas -- Thomas Kähn WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0 tk@westend.com Internet & Security for Professionals Fax 0241/911879 WESTEND ist CISCO Systems Partner - Premium Certified _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
On Thursday, February 07, Nicholas Berry wrote:
I didn't see if any mailed in a resolution to this problem, I'm still having it. I'm running Solaris 8 (SPARC) w/syslog-ng-1.5.13 and libol-0.3.1. Also, when I run more or less on one of the log files, I occassionally get the error "file may be a binary, continue?"
I too get high ASCII characters, but on a regular basis across multiple systems. I have about 20 hosts logging to two syslog-ng systems. I see this anywhere from
I've seen them too, only intermixed with sendmail logging. Also Solaris 8 SPARC, with syslog-ng 1.4.x and 1.5.x. Could syslog-ng be taught to strip out any unprintables? It would make parsing the logs that much easier. Perhaps as a log { } option, so if you wanted them, you could keep it? -- Key fingerprint = AB4B 584D B0FF D770 2B70 10B5 5708 E111 9A52 9B97 "There are no mistakes, only happy accidents." -- Bob Ross
participants (2)
-
Nicholas Berry
-
William Yodlowsky