Just experienced the same issue again. Rsyslog version 8.15.0 crashed after the FS for queues got full.
Mar 23 08:29:49 server kernel: [23586716.165832] rs:STRMEP2 queu[31413]: segfault at 1 ip 00007f90dc66b34c sp 00007f90d99daa40 error 4 in rsyslogd[7f90dc645000+90000] Recovered most of the queue by removal of the oldest queue file. Removal of the queue file from the crash (the newest one) didn't help. -- Peter On Fri, Feb 17, 2017 at 9:02 AM, Peter Viskup <[email protected]> wrote: > Sorry for not to mentioned. > The qi file was rebuilt. Once I moved the files out, the rsyslog > started just fine. I have a copy of the whole queue, thus can be used > for further investigation. > Are we able to check the consistency of queue files somehow? > > -- > Peter > > On Thu, Feb 16, 2017 at 3:44 PM, David Lang <[email protected]> wrote: >> odds are that the queue files have been corrupted. you need to rebuild the >> .qi file and then it should be able to startup. >> >> David Lang >> >> On Thu, 16 Feb 2017, Peter Viskup via rsyslog wrote: >> >>> Date: Thu, 16 Feb 2017 13:50:37 +0100 >>> From: Peter Viskup via rsyslog <[email protected]> >>> To: rsyslog-users <[email protected]> >>> Cc: Peter Viskup <[email protected]> >>> Subject: [rsyslog] Rsyslog with queue files won't start >>> >>> >>> Just experienced issue with rsyslog with DA queue files. >>> The process just died without any error. >>> We do run rsyslog version 8.15.0 >>> These are the last lines from debug output >>> >>> 8488.225603049:STRMEP2 queue[DA]:Reg/w0: omfwd: beginTransaction >>> 8488.225606660:STRMEP2 queue[DA]:Reg/w0: 10.1.25.181 >>> 8488.225610889:STRMEP2 queue[DA]:Reg/w0: Action 4 transitioned to state: >>> itx >>> 8488.225614575:STRMEP2 queue[DA]:Reg/w0: Action 4 transitioned to state: >>> rdy >>> 8488.225618011:STRMEP2 queue[DA]:Reg/w0: actionCommit, in retry loop, iRet >>> 0 >>> 8488.225622069:STRMEP2 queue[DA]:Reg/w0: regular consumer finished, >>> iret=0, szlog 128708 sz phys 128716 >>> 8488.225631031:STRMEP2 queue[DA]:Reg/w0: DeleteProcessedBatch: we >>> deleted 8 objects and enqueued 0 objects >>> 8488.225635210:STRMEP2 queue[DA]:Reg/w0: doDeleteBatch: delete batch >>> from store, new sizes: log 128708, phys 128708 >>> 8488.225672091:STRMEP2 queue[DA]:Reg/w0: strm 0x7f0761c13b40: file 11 >>> read 4096 bytes >>> 8488.225760644:STRMEP2 queue[DA]:Reg/w0: strm 0x7f0761c13b40: file 11 >>> read 4096 bytes >>> 8488.225864111:STRMEP2 queue[DA]:Reg/w0: strm 0x7f0761c13b40: file 11 >>> read 4096 bytes >>> 8488.225966025:STRMEP2 queue[DA]:Reg/w0: strm 0x7f0761c13b40: file 11 >>> read 4096 bytes >>> 8488.225977652:STRMEP2 queue[DA]:Reg/w0: error -2059 deserializing >>> property name, offset 208904, step 2 >>> 8488.225984716:STRMEP2 queue[DA]:Reg/w0: error property name: 'msg<Obj' >>> 8488.225991530:STRMEP2 queue[DA]:Reg/w0: error var type: '1' >>> >>> What's going wrong here? >>> >>> >> _______________________________________________ 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.
