I would actually start with "git log" or the change log and pick those patches targeted towards the queue code.
The debug log will probably not have the exact cause, but will show you what happened around the time of the abort. HTH Rainer El vie., 24 ene. 2020 a las 9:33, Peter Viskup via rsyslog (<[email protected]>) escribió: > > Experience regular segfaults on one rsyslog 8.15 instance. I know it is old > version, but still would like to trace it as am not able to upgrade ATM. > Seems it is caused by writing some message to DA cache (or by reading it > from). > > Would it be possible to find it in debug log (already got it)? What should > I look for? > > Error message: > Jan 24 08:54:25 hostname kernel: [38302481.667884] rs:FWD queue[DA[6533]: > segfault at 20 ip 0000560e6b9c834c sp 00007f877ae83a40 error 4 in > rsyslogd-lin[560e6b9a2000+90000] > > Thank you. > > -- > Peter > _______________________________________________ > 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. _______________________________________________ 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.
