[syslog-ng]Some device doesn't write to file
Santa Lau
syslog-ng@lists.balabit.hu
Mon, 27 Oct 2003 16:36:21 +0800
This is a multi-part message in MIME format.
------=_NextPart_000_0123_01C39CA8.73F7BC00
Content-Type: text/plain;
charset="big5"
Content-Transfer-Encoding: quoted-printable
Hi,
I just upgrade the hardware and software of the syslog-ng server to =
1.60rc4 from 1.5 to log about 30 firewalls syslog. After upgarde, I did =
find that nearly half of the firewalls log doesn't write to the file. I =
did check with tcpdump and it did receive the tons of logs but did't log =
into the file. The iptables/ipchains has all been disabled. Is there =
any way to identify the source of problem. Thanks for your help.
B. Regards,
Santa
------=_NextPart_000_0123_01C39CA8.73F7BC00
Content-Type: text/html;
charset="big5"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dbig5">
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><STRONG><FONT face=3DArial size=3D2>Hi,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial size=3D2></FONT></STRONG> </DIV>
<DIV><STRONG><FONT face=3DArial size=3D2>I just upgrade the hardware and =
software of=20
the syslog-ng server to 1.60rc4 from 1.5 to log about=20
30 firewalls syslog. After upgarde, I did find =
that nearly=20
half of the firewalls log doesn't write to the =
file. I did=20
check with tcpdump and it did receive the tons of logs but did't log =
into the=20
file. The iptables/ipchains has all been disabled. =20
</FONT></STRONG><STRONG><FONT face=3DArial size=3D2>Is there any way to =
identify the=20
source of problem. Thanks for your help.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial size=3D2></FONT></STRONG> </DIV>
<DIV><STRONG><FONT face=3DArial size=3D2>B. =
Regards,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial =
size=3D2>Santa</FONT></STRONG></DIV></BODY></HTML>
------=_NextPart_000_0123_01C39CA8.73F7BC00--