[rsyslog-notify] Forum Thread: Re: imptcp not writing to file - (Mode 'reply')

noreply at adiscon.com noreply at adiscon.com
Wed May 25 17:29:35 CEST 2016


User: re-su 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=26540#p26540

Message: 
----------
For all with the same problem (as I had as well): it seems to be a problem
of "logger". At least on SLES 12, logger with tcp seems not to follow the
syslog-protocol and rsyslog on the other side receives the message but
doesn't want to write anything, as we see in the debug messages. BTW: using
logger with udp and the same message works fine.

As I don't have the time to analyze the tcpdumps and to find the right
rsyslog mechanism to write anything it gets, I just changed the logger-test
...

Just use following simple perl script for remote tcp logging tests:

use Sys::Syslog qw(:DEFAULT setlogsock);
setlogsock({ type => "tcp", port => [b:1fsmwklx]6514[/b:1fsmwklx] });
$Sys::Syslog::host = "[b:1fsmwklx]Remotehost[/b:1fsmwklx]";
openlog($program, 'ndelay', 'user');
syslog('info', 'bridge over trouble water - fo');
closelog();

Change Port (6514) and Remotehost and try it. 

This worked fine for me.
Cheers, Res


More information about the rsyslog-notify mailing list