> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Marc Schiffbauer > Sent: Tuesday, October 13, 2009 3:32 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 4.5.x queue file cleanup? > Am Dienstag, 13. Oktober 2009 14:16:47 schrieb Rainer Gerhards: > > This looks like a dirty shutdown. > > I am not aware of any... > > > In general, rsyslog cleans up when > > processing completes. > > OK. This is good to know. So something went wrong here: I produced a > lot of > logging traffic using the logger shell command. Then I stopped that > postgres > server to test that spooling works. After a while I started it again. > After a while rsyslog reconnected to the db and logging to the DB was > working > again. > > > > Do you have a .qi file inside that directory? Absence > > of a .qi file - when the instance is not running - is indication of > an > > issue during shutdown. > > There is a .qi file when rsyslog is NOT running and ist being removed > when I > start it again.
That is OK, because then rsyslog keeps the information in memory once it runs, to safe i/o time. You can modify that by specifying a different queue configuration, but you need to understand how the queue system works in order to do so. A good read is the queue doc. Rainer > > I will remove stop rsyslog now, then remove *everything* from the > spool- > directory and start it up again. > > Then I will repeat the spool-test. > > Thanks for helping > -Marc > > > > > Rainer > > > > > -----Original Message----- > > > From: [email protected] [mailto:rsyslog- > > > [email protected]] On Behalf Of Marc Schiffbauer > > > Sent: Tuesday, October 13, 2009 1:21 PM > > > To: [email protected] > > > Subject: [rsyslog] rsyslog 4.5.x queue file cleanup? > > > > > > Hello all, > > > > > > I am running a rsyslog server version 4.5.2 > > > > > > I tested the message queuing capabilities recently and noticed that > > > queue > > > files do not get cleaned up. Evertime rsyslog has to spool > something > > > (e.g. > > > when the database server ist stopped) it creates new spoolfiles so > the > > > spool > > > area will grow over time. > > > > > > Is this a bug or how can I handle those old queue files? > > > > > > This is the relevant part from my config: > > > > > > # enable message spooling > > > $WorkDirectory /data/syslog-spool # default location for work > (spool) > > > files > > > $ActionQueueType LinkedList # use asynchronous processing > > > $ActionQueueFileName dbq # set file name, also enables > disk > > > mode > > > $ActionResumeRetryCount -1 # infinite retries on insert > failure > > > > > > > > > TIA > > > -Marc Schiffbauer > > -- > Senior Consultant :: Solution Architect > IT-Security :: Free Software :: GNU/Linux > Mobile +49_151_16227402 :: Fon +49_6187_9058695 :: Fax +49_6187_900157 > MightyCare Solutions GmbH http://www.mightycare.de > Firmenangaben unter http://www.mightycare.de/#/de/impressum/ > _______________________________________________ > 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
