[rsyslog] rsyslogd not reconnecting when using tcp or omrelptransports

Rainer Gerhards rgerhards at hq.adiscon.com
Fri Sep 11 12:13:12 CEST 2009


I suggest to turn on debug logging on both the client and sender:

http://www.rsyslog.com/doc-troubleshoot.html

Often, the debug log points to an obvious problem source. If it does not,
feel free to mail me the logs to rgerhards at gmail.com BUT let me know you did
so - I usually do not monitor this account.

Rainer 

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Thomas Mieslinger
> Sent: Friday, September 11, 2009 11:47 AM
> To: rsyslog-users
> Subject: [rsyslog] rsyslogd not reconnecting when using tcp or
> omrelptransports
> 
> Hi,
> 
> I've setup rsyslog on CentOS 5.3 (rsyslog-3.21.3-4) on two machines.
> One
> machine (logsender) has:
> 
> $ModLoad omrelp.so
> $WorkDirectory /var/spool/rsyslog
> $ActionQueueType LinkedList
> $ActionQueueFileName srvrfwd
> $ActionResumeRetryCount -1
> $ActionQueueSaveOnShutdown on
> 
> user.* :omrelp:loghost:2514
> or
> user.* @@loghost:1514
> 
> and the other machine (loghost)
> has
> 
> $ModLoad imrelp.so
> $UDPServerRun 514
> $InputTCPServerRun 1514
> $InputRELPServerRun 2514
> 
> *.* -/some/logfile
> 
> If I restart rsyslog on loghost without restarting rsyslog on
> logsender,
> the logs produced on logsender never appear on loghost. Is this working
> as designed?
> 
> Is there a kind of syslog.debug facility where I can monitor the
> reconnect activity of rsyslog?
> 
> Thanks in advance Thomas
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com



More information about the rsyslog mailing list