<br><font size=2 face="sans-serif">I recently upgraded to syslog-ng 2.0.4
running on a Red Hat AS release 4. I have the following on
the system:</font>
<br>
<br><font size=2 face="sans-serif">eventlog-0.2.5-1.i386.rpm</font>
<br><font size=2 face="sans-serif">eventlog-devel-0.2.5-1.i386.rpm</font>
<br><font size=2 face="sans-serif">libnet-devel-1.1.2.1-6.i386.rpm</font>
<br><font size=2 face="sans-serif">syslog-ng-2.0.4-1.i386.rpm</font>
<br>
<br>
<br><font size=2 face="sans-serif">When I fire up syslog-ng I receive a
large number of the following:</font>
<br>
<br><font size=2 face="sans-serif">Aug 30 14:36:07:2007 syslogger1 syslog-ng[31079]:
Error sending raw frame; error=\'libnet_write_raw_ipv4(): -1 bytes written
(Message too long)\\x0a\'</font>
<br><font size=2 face="sans-serif">Aug 30 14:36:07:2007 syslogger1 syslog-ng[31079]:
Error sending raw frame; error=\'libnet_write_raw_ipv4(): -1 bytes written
(Message too long)\\x0a\'</font>
<br><font size=2 face="sans-serif">Aug 30 14:36:07:2007 syslogger1 syslog-ng[31079]:
Error sending raw frame; error=\'libnet_write_raw_ipv4(): -1 bytes written
(Message too long)\\x0a\'<br>
</font>
<br>
<br><font size=2 face="sans-serif">I am trying to forward packets onto
another log product, so I have spoof_source(yes) specified. What
is the remedy for this error, am I loosing data?</font>
<br>
<br><font size=2 face="sans-serif">Please advise,</font>
<br><font size=2 face="sans-serif">Jim</font>
<br><font size=2 face="sans-serif"><br>
</font>
<P><hr size=1></P>
<P><STRONG>
This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.
</STRONG></P>