For those who will experience the same issue. Decided to rename the files not following the index order and recovered index and queue was emptied. Am looking forward to implement newer version. Hopefully not as many issues will raise and most of these will be solved. :-)
On Mon, Jun 29, 2015 at 2:09 PM, Peter Viskup <[email protected]> wrote: > We have server with TLS forward. All seems to be fine except the forward > and main DA queues got full, rsyslog crashed and now there are some issues > with the DAq files. > The queues are not emptying and recover script reports broken queue. > > root@server:~# /usr/local/sbin/recover.qi.pl -w /var/log -f main_queue -d > 8 > /var/log/main_queue.qi > broken queue: missing file(s) or wrong > > Had a look into script and found there is issue with continuity of the DAq > files: > First file is: /var/log/main_queue.00000140 > and second: /var/log/main_queue.00000293 > > The newest file is that one with the 140 index. How could that happen? We > are still running old Debian version. > May I omit that check from the recovery script to not loose any messages? > Or just to rename the 140 file to 292? What's the better procedure? > > Thank you. > > -- > Peter Viskup > _______________________________________________ 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 NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
