This sounds like another incarnation of a problem with the Ubuntu package. See this bug tracker:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 If you think this is the reason, please make yourself heard. It would be really great if Ubuntu finally fixed the issue... Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Chris Toomey > Sent: Wednesday, September 07, 2011 8:14 AM > To: [email protected] > Subject: [rsyslog] NFS log files not re-opened after rotation > > We've recently switched our Apache 2.x configuration to log indirectly > via > rsyslog rather than directly to the log files, in order to get the > benefits > of asynchronous logging (we see periodic latency spikes when logging to > our > NFS filer). > > When the rsyslog-generated Apache log files are on a local disk, the > nightly > log rotation (which triggers an rsyslog reload == HUP signal) works > fine. > But when the log files are on an NFS filer, for some reason rsyslogd > doesn't > re-open them after the HUP -- lsof on the rsyslogd process shows the > log > files open before but not after the HUP. Doing a restart of rsyslogd > does > open them again. > > We're using rsyslog 4.2.0, which is the version distributed with our > Ubuntu > 10.10. > > Any ideas on why rsyslog is responding differently to the HUP for local > vs. > NFS log files and what to do to make it work for NFS log files? > > I ran rsyslogd with -dn and captured the debug output across the HUP > processing both when using local and NFS files, but didn't see anything > obvious about why the log files weren't reopened when over NFS. > > Thanks for any help. > Chris > _______________________________________________ > 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
