> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: Thursday, July 05, 2012 10:10 AM > To: rsyslog-users > Subject: Re: [rsyslog] separate local disk and nfs queues > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Radu Gheorghe > > Sent: Thursday, July 05, 2012 10:01 AM > > To: rsyslog-users > > Subject: Re: [rsyslog] separate local disk and nfs queues > > > > OK, so I really was totally wrong. I'll do more research next time > > before replying... > > The problem is that the config is totally counter-intuitive. In v6, things are > much easier to grasp, as the queue params are set within the action itself. > Have a look here: > > http://www.rsyslog.com/doc/node32.html
I've made a quick example of old vs nw style: http://blog.gerhards.net/2012/07/rsyslog-action-queue.html > Rainer > PS: Florian is currently working on (somewhat) better doc :-) > > > 2012/7/5 Rainer Gerhards <[email protected]>: > > >> I might be totally wrong here, but my understanding is that you can > > >> only have one queue for the action queue. So the "NAS" and "LOCAL" > > >> part seem to be overlapping in that area. > > > > > > I am not sure if I understood you correctly. Each action has a > > > dedicated > > queue. This queue can be in-memory, it can be on disk and it can be a > > combination of both. There is also direct mode, which means by desing > > there is a queue but the actual driver does forward messages to the > > action without action queing. > > > > > > When you define actions, the queue parameters belong to the *next* > > action (in v6 this is far easier to understand and see as the queue > > params are specified within the action). In the snippet below, we have > > two actions, and each of them is configured with different queue > > settings. This results with two different sets of queue files being > > written. It is important that the queue file names are different (as > > they are), but otherwise the queues are independent. There can be as > many disk (or DA) queues as there are actions. > > Note that if there is only a single action queue and n actions, this > > means only one action uses the disk queue, whereas n-1 actions do not > > use it (if nothing else is set, they run in direct mode). > > > > > > In that sense, the config looks OK to me. However, I am a bit > > > skeptic on the NFS mount in general, I know several users have > > > reported problems of various kinds with such configs. Maybe many > > > more happily use the same ;) > > > > > > Hope this clarifies, > > > Rainer > > >> > > >> Best regards, > > >> Radu > > >> > > >> 2012/7/5 ignasr ignasr <[email protected]>: > > >> > Hello, is this a sane config? I am trying to save incoming remote > > >> > logs to an NFS mount, and to local disk in case NFS hard locks > > >> > for some time. Maybe LOCAL part is not needed at all? > > >> > > > >> > **** > > >> > $template > > >> > Tdefault,"/logs/syslog/%fromhost- > > >> ip%/%$YEAR%/%$MONTH%/%syslogfacility-text%.%$YEAR%- > > %$MONTH%- > > >> %$DAY%.log" > > >> > $template > > >> > TdefaultBackup,"/var/log/backups/%fromhost-ip%.%$YEAR%- > > >> %$MONTH%-%$DAY%.log" > > >> > $template > > >> > Tcritical,"/logs/syslog/%fromhost- > > >> ip%/%$YEAR%/%$MONTH%/critical.%$YEAR%-%$MONTH%- > %$DAY%.log" > > >> > $template FileFormat,"%TIMESTAMP:::date-rfc3339% %HOSTNAME% > > >> > %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n" > > >> > > > >> > $WorkDirectory /var/log/rsspool > > >> > > > >> > # NAS > > >> > $ActionQueueType LinkedList # use asynchronous processing > > >> > $ActionQueueFileName nfsq # set file name, also enables disk mode > > >> > $ActionResumeRetryCount -1 # infinite retries on insert failure > > >> > *.err -?Tcritical;FileFormat > > >> > *.* > > >> > -?Tdefault;FileFormat > > >> > > > >> > # LOCAL > > >> > $ActionQueueType LinkedList # use asynchronous processing > > >> > $ActionQueueFileName diskq # set file name, also enables disk > mode > > >> > $ActionResumeRetryCount 0 # default > > >> > *.* > > >> > -?TdefaultBackup;FileFormat > > >> > **** > > >> > > > >> > Thank you, > > >> > IgnasR > > >> > _______________________________________________ > > >> > rsyslog mailing list > > >> > http://lists.adiscon.net/mailman/listinfo/rsyslog > > >> > http://www.rsyslog.com/professional-services/ > > >> > What's up with rsyslog? Follow https://twitter.com/rgerhards > > >> _______________________________________________ > > >> rsyslog mailing list > > >> http://lists.adiscon.net/mailman/listinfo/rsyslog > > >> http://www.rsyslog.com/professional-services/ > > >> What's up with rsyslog? Follow https://twitter.com/rgerhards > > > _______________________________________________ > > > rsyslog mailing list > > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > > http://www.rsyslog.com/professional-services/ > > > What's up with rsyslog? Follow https://twitter.com/rgerhards > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com/professional-services/ > > What's up with rsyslog? Follow https://twitter.com/rgerhards > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards
