repost: line truncation with spamd
Is anyone looking into this issue? To refresh your memory, all five of these entries appear on the same line: 2004-12-09T01:09:35+1000 chloe spamd[704]: connection from localhost [127.0.0.1] at port 40811 2004-12-09T01:09:35+1000 chloe spamd[13558]: info: setuid to slittle succeeded 2004-12-09T01:09:35+1000 chloe spamd[13558]: processing message <35089309.09501@cbuki@getherbalnow.info> for slittle:1000. 2004-12-09T01:09:36+1000 chloe spamd[13558]: identified spam (20.8/5.0) for slittle:1000 in 0.8 seconds, 1475 bytes. 2004-12-09T01:09:36+1000 chloe qmail: 1102514976.416174 new msg 12808775
I am running syslog-ng 1.6.5 and spamassasin 3.01 on linux without a problem. What OS and versions are on your end? On Thu, 09 Dec 2004 01:42:59 +1000, scott <syslogng@slittle.com> wrote:
Is anyone looking into this issue?
To refresh your memory, all five of these entries appear on the same line:
2004-12-09T01:09:35+1000 chloe spamd[704]: connection from localhost [127.0.0.1] at port 40811 2004-12-09T01:09:35+1000 chloe spamd[13558]: info: setuid to slittle succeeded 2004-12-09T01:09:35+1000 chloe spamd[13558]: processing message <35089309.09501@cbuki@getherbalnow.info> for slittle:1000. 2004-12-09T01:09:36+1000 chloe spamd[13558]: identified spam (20.8/5.0) for slittle:1000 in 0.8 seconds, 1475 bytes. 2004-12-09T01:09:36+1000 chloe qmail: 1102514976.416174 new msg 12808775
I am running syslog-ng 1.6.5 and spamassasin 3.01 on linux without a problem. What OS and versions are on your end?
Debian Testing and Debian Stable. A recent upgrade to SA 3.01 didn't fix it. Nor did compiling syslog-ng from source.
On Wed, 2004-12-15 at 16:40, scott wrote:
I am running syslog-ng 1.6.5 and spamassasin 3.01 on linux without a problem. What OS and versions are on your end?
Debian Testing and Debian Stable.
A recent upgrade to SA 3.01 didn't fix it. Nor did compiling syslog-ng from source.
I think the problem is caused by a bug in syslog-ng in which it includes NUL characters in the message, e.g. it tries to write something like $MSG\0\n, thus the line is truncated by the '\0' character. it is triggered only with unix-dgram and udp sources, but I didn't have time to look into it. Can you check whether switching over to using unix-stream sources solves your problem? -- Bazsi
Yep, so far so good.
Can you check whether switching over to using unix-stream sources solves your problem?
participants (3)
-
Balazs Scheidler
-
Jay Guerette
-
scott