Am Dienstag, 13. Oktober 2009 15:41:17 schrieb Rainer Gerhards:
> >
> > 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.
> >
As it seems, rsyslog will not write a .qi file in all cases.
New tests were not all successful (with rsyslog under load):
OK => spooling while DB is offline
OK => reconnect to DB
OK => despooling while still under load and spooling to disk
Now the following produced "stale" queue files and a loss of messages I guess:
NOT OK => despooling while under load and while spooling to disk,
then stopping rsyslogd
(stopped via /etc/init.d/syslog stop)
-> no .qi file has been created!
after making sure there are no more rsyslog processes I started it again.
The spool files will not be cleared (no load anymore and DB started of course)
bug?
TIA
-Marc
--
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
