We are in need of a solution to move many different kinds of logs across our network. Traditionally our developers have pretty much just dumped log files where ever which of course is unmanagable after a while. We are currently using NG with Apache and are comfortable with the idea of loosing a log every now and then. What we cannot do is loose logs that our developer's applications are sending to the server. It appeared that a good way to accomplish this would be to use the TCP functionality built into NG. I have had some difficulty getting NG to accept the parameters listed on the docs page for the TCP connection. I even copied them verbatim at one point and still receive a parse error on the destination line in question. So, Two questions I guess: 1.) Can the TCP functionality be used as a fault tolerant solution for our developers logging needs? 2.) Does anyone have any suggestion as to why the following line would fail? destination d_joust { tcp("192.168.30.225" port(1999); localport(999)); }; <------------ Line 22 causing the parse error. filter f_tcp { (level(info) and facility (local7)); } log { source(s_sys); filter(f_tcp); destionation(d_joust); }; parse error at 22 Parse error reading configuration file, exiting. Thanks for any suggestions. -JMc
On Mon, Nov 11, 2002 at 04:23:38PM -0600, Jeff McReynolds wrote:
We are in need of a solution to move many different kinds of logs across our network. Traditionally our developers have pretty much just dumped log files where ever which of course is unmanagable after a while. We are currently using NG with Apache and are comfortable with the idea of loosing a log every now and then. What we cannot do is loose logs that our developer's applications are sending to the server. It appeared that a good way to accomplish this would be to use the TCP functionality built into NG. I have had some difficulty getting NG to accept the parameters listed on the docs page for the TCP connection. I even copied them verbatim at one point and still receive a parse error on the destination line in question.
So, Two questions I guess:
1.) Can the TCP functionality be used as a fault tolerant solution for our developers logging needs?
2.) Does anyone have any suggestion as to why the following line would fail?
destination d_joust { tcp("192.168.30.225" port(1999); localport(999)); }; <------------ Line 22 causing the parse error.
destination d_joust { tcp("192.168.30.225" port(1999) localport(999)); }; the ';' after port() is not needed. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
Jeff McReynolds