> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Dirk > Sent: Friday, January 28, 2011 2:36 PM > To: rsyslog-users > Subject: [rsyslog] Missing input file unnerving rsyslogd - was: Re: > Rsyslog and FIN_WAIT1 > > Hi all, > > I have tracked the problem down: if rsyslog is configured to read > messages from a log file and the file does not exist, it does not > - refrain from starting > - place relevant messages somewhere > or anything sensible. It starts the weird behaviour I described even up > to TCP connections hanging in FIN_WAIT1 for ever. > > Is this a known bug of 3.18.3? This is the RPM from SLES11.
sounds so > > Is this solved in a later release? very probably, as I did a couple of changes to imfile recently. Note that v3 is no longer officially supported, so the fixes went into v4 and above. Rainer > > Or do I misunderstand something completely? > > Dirk > > Am 27.01.11 17:54, schrieb Dražen Kačar: > > Dirk wrote: > > > >> Now, if the tcp connection does not leave FIN_WAIT1 state (may be > the > >> TCP ACK does not reach the client for network reasons) the client > >> rsyslog stops all activity (writing to local logs, importing local > logs, > >> etc.) and does not write anything into the queue buffer files. In > fact > >> it seems dead until rebooted. > > Can you run strace on the client when this happens? My guess is that > it will > > be hanging in the close() syscall. > > > > _______________________________________________ > 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
