Hi, thanks for the debug log anyhow. After lookig at it, I think it is related to the programname filter, and that in turn be related to some malformed message. So, at quick glimpse, everything seems to be OK as far as rsyslog is concerned. As you have solved the issue, I'll not dig deeper into it, except someone else comes up with a problem scenario.
Thanks, Rainer > -----Original Message----- > From: Stefano Coletta [mailto:[email protected]] > Sent: Thursday, June 24, 2010 10:29 AM > To: Rainer Gerhards > Subject: Re: [rsyslog] FreeBSD 6.4 and rsyslog 4.3.0 remote logging (as > client) doesn't work > > Hello, > thank you for your help. > > To tell the truth I've replaced rsyslog with syslog-ng in the mean time > because the latter has worked for me out of the box. > > I'm using rsyslog for all our linux systems and I wanted to use it even > for our BSD systems before being stopped with this problem. > > Anyway the debug log is attached, thank you for your kind support. > > Greetings, > Stefano Coletta > > Unidata S.p.a. > Via Portuense, 1555 - 00143 Roma > Commercity - Modulo M25 > Tel +39 06404041 > Fax +39 0640404002 > E-mail [email protected] > > On 22/06/2010 11.09, Rainer Gerhards wrote: > >> -----Original Message----- > >> From: [email protected] [mailto:rsyslog- > >> [email protected]] On Behalf Of Stefano Coletta > >> Sent: Monday, June 21, 2010 5:59 PM > >> To: [email protected] > >> Subject: [rsyslog] FreeBSD 6.4 and rsyslog 4.3.0 remote logging (as > >> client) doesn't work > >> > >> Hello, > >> I've installed rsyslog 4.3.0 on a freebsd 6.4-RELEASE-p6 i386 and > >> unfortunately I cannot send any syslog data to a remote server by > using > >> the standard configuration directive: > >> > >> *.* @192.168.0.1 > >> > >> or > >> > >> *.* @@192.168.0.1 > >> > >> By using tcpdump, as far I can see, *no packets* go out from the > >> freebsd > >> system (nor tcp or udp) to reach the remote syslog server > 192.168.0.1. > >> > >> The remote server 192.168.0.1 is obviously reachable: I can make a > >> telnet session to the port 514/tcp from the freebsd server. > >> > >> Enabling debug info not helped, it seems there is no error anywhere. > > > > You probably were not able to fully interpret it (it's not easy). If > you mail > > me a copy privately (the list will probably reject it due to size > and/or > > format), I'll have a look and check if I see something. > > > > Rainer > > > >> > >> This is how it has been compiled: > >> > >> rsyslog will be compiled with the following settings: > >> > >> Multithreading support enabled: yes > >> Klog functionality enabled: yes (bsd) > >> Regular expressions support enabled: yes > >> Zlib compression support enabled: yes > >> MySql support enabled: no > >> libdbi support enabled: no > >> PostgreSQL support enabled: no > >> Oracle (OCI) support enabled: no > >> SNMP support enabled: no > >> Mail support enabled: yes > >> RELP support enabled: no > >> imdiag enabled: no > >> file input module enabled: yes > >> input template module will be compiled: yes > >> output template module will be compiled: no > >> omprog module will be compiled: no > >> omstdout module will be compiled: no > >> Large file support enabled: yes > >> Networking support enabled: yes > >> GnuTLS network stream driver enabled: no > >> Enable GSSAPI Kerberos 5 support: no > >> Debug mode enabled: no > >> Runtime Instrumentation enabled: no > >> Diagnostic tools enabled: no > >> valgrind support settings enabled: no > >> rsyslog runtime will be built: yes > >> rsyslogd will be built: yes > >> > >> >From -v switch: > >> > >> [r...@server]# rsyslogd -v > >> rsyslogd 4.3.0, compiled with: > >> FEATURE_REGEXP: Yes > >> FEATURE_LARGEFILE: Yes > >> FEATURE_NETZIP (message compression): Yes > >> GSSAPI Kerberos 5 support: No > >> FEATURE_DEBUG (debug build, slow code): No > >> Atomic operations supported: No > >> Runtime Instrumentation (slow code): No > >> > >> This is the first time I use rsyslog on a freebsd system. > >> > >> Any ideas? > >> > >> Thank you in advance. > >> > >> -- > >> Greetings, > >> Stefano Coletta > >> > >> Unidata S.p.a. > >> Via Portuense, 1555 - 00143 Roma > >> Commercity - Modulo M25 > >> Tel +39 06404041 > >> Fax +39 0640404002 > >> E-mail [email protected] > >> _______________________________________________ > >> rsyslog mailing list > >> http://lists.adiscon.net/mailman/listinfo/rsyslog > >> http://www.rsyslog.com > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
