Invalid frame header messages
Hi everyone, I compiled version 3.3.3 and tried getting a client and server to talk based on the documentation on the balabit site, specifically the documentation for OSE version 3.3. The server config file: -- source remotelogs { syslog( port(2072) transport(tcp) ); } ; destination r_log { file("/var/log/remotelogs/all"); }; log{ source(remotelogs); destination(r_log); } ; -- And the client sending: -- # remote logging test log # @version: 3.3 source s_kern { file("/proc/kmsg"); }; source s_local { unix-stream("/dev/log"); internal(); }; destination d_file {file("/var/log/messages"); }; destination d_secure { file("/var/log/secure");}; # set the filters filter f_messages { not facility(auth, authpriv);}; filter f_authpriv { facility(auth, authpriv); }; destination loghost { tcp(10.195.105.214 port(2072) ); }; log { source(s_kern) ; source(s_local) ; filter(f_messages) ; destination(loghost) ; } ; -- There are some other log directives there for local files, I'll post them if people want to see them So when this runs, I get on the server: Dec 7 11:18:05 xxxxxxxxxx syslog-ng[4188]: Syslog connection closed; fd='21', client='AF_INET(10.203.54.9:54837)', local='AF_INET(0.0.0.0:2072)' And the client: Dec 7 11:19:04 xxxxxxxxxxxx syslog-ng[1735]: Syslog connection established; fd='20', server='AF_INET(10.195.105.214:2072)', local='AF_INET(0.0.0.0:0)' I read the email thread from 2009, and tried the vanilla configs - any ideas? Thanks, Jan
While playing with the configurations some more, running UDP works. Do TCP formats have to be explicitly defined, like someone did in the "simple config question" thread? Thanks, Jan
source remotelogs { syslog( port(2072) transport(tcp) ); } ;
Wednesday 07 of December 2011 17:26:06 Mr. Jan Walter wrote:
I compiled version 3.3.3 and tried getting a client and server to talk based on the documentation on the balabit site, specifically the documentation for OSE version 3.3.
The server config file: -- source remotelogs { syslog( port(2072) transport(tcp) ); } ;
You are using syslog() source driver on your server, but...
And the client sending: -- [...] destination loghost { tcp(10.195.105.214 port(2072) ); };
... plain tcp() destination driver on your client. Change it to syslog() so they match. http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.3-guide... HTH -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D
Doh! Thanks. The syntax between tcp and syslog declarations strikes me as a bit irregular - one takes ip() as an argument and the other does not. Cheers, Jan
________________________________ From: Jakub Jankowski <shasta@toxcorp.com> To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Sent: Wednesday, December 7, 2011 12:13 PM Subject: Re: [syslog-ng] Invalid frame header messages
Wednesday 07 of December 2011 17:26:06 Mr. Jan Walter wrote:
I compiled version 3.3.3 and tried getting a client and server to talk based on the documentation on the balabit site, specifically the documentation for OSE version 3.3.
The server config file: -- source remotelogs { syslog( port(2072) transport(tcp) ); } ;
You are using syslog() source driver on your server, but...
And the client sending: -- [...] destination loghost { tcp(10.195.105.214 port(2072) ); };
... plain tcp() destination driver on your client. Change it to syslog() so they match.
http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.3-guide...
HTH
-- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
On Wed, 2011-12-07 at 10:29 -0800, Mr. Jan Walter wrote:
Doh! Thanks.
The syntax between tcp and syslog declarations strikes me as a bit irregular - one takes ip() as an argument and the other does not.
It's not a difference betwen tcp and syslog, but rather source and destination. On the source side, no parameter is required, on the destination side the name of the server is required, thus it is a positional parameter, rather than an option. However this question has been brought up so many times, that I'd be willing to integrate an alternative syntax if someone has the time to prepare a patch. Thanks. -- Bazsi
participants (3)
-
Balazs Scheidler
-
Jakub Jankowski
-
Mr. Jan Walter