On Tue, 2008-07-29 at 22:58 -0700, Rory Toma wrote: > Rainer Gerhards wrote: > > I don't see any obvious error and, yes, the queue files should be > > deleted. Actually, you should only see any files at all if the inserts > > take too long. What you have may be an artifact of a previous failure. > > > > To get down to what it is, we need to check how things progress. Is your > > database populated? In any case, a debug log (rsyslogd with -dn > > additional options run interactively) will tell us what is there. Also, > > there should be a .qi file. Let us know its contents. > > > > Thanks, > > Rainer > > > > > the db is getting populated and there is no .qi file.
No .qi file is a good indication (though not sufficient) that the queue files are artifacts of a previous failure. > If I run in with > "-dn" there is a ton of output, so I need to know what to look for. I've > been running for about a day, and I'm at 20+ million records. I usually know only when I see. Based on this case, I'd be interested in the first 2000 lines and another 1000 lines while it is processing records. That should at least provide enough of a clue to ask for something more specific. > > I do get an error -2040 when accessing on-disk files. Should I just nuke > these? This can be OK. I think you see the -2040 (file not found) when it is looking for the .qi files. Rainer > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
