Sent from phone, thus brief. Am 03.11.2016 21:01 schrieb "singh.janmejay" <[email protected]>: > > Pulled the attachments down, I don't have enough information to say > this yet, but it does seem like memory corruption. > > Statement that scriptExec is trying to execute is at 0x30e1, if you > still have the corefile, can you please check if that address is > mapped RW? > > Another funny thing is, you seem to have 2021 threads (almost all > timed-waiting inside asyncWriterThread function). I haven't seem strm > code, so not sure why it'd spawn this large number of threads. > Something for us to check.
This strongly sounds like a large dynafile cache with background writing turned on (where each cached file has its background writer thread). Background writing usually is not a good idea (except you know exactly why you need it), and with a large cache it's almost always a bad idea. > > If this is indeed memory corruption running with valgrind may help > validate (if we are lucky, it may even help find the starting point of > corruption). In my experience, valgrind unfortunately does not help much when many threads are involved (as it has no real concurrency). ASAN is *much* better here, I have made excellent experiences with it under such circumstances. The downside if that you need to rebuild with the -fsanitze=address flag. Just my 2cts, Rainer > > On Wed, Nov 2, 2016 at 10:56 PM, shane.lawrence > <[email protected]> wrote: > > I uploaded it to nabble and there is a link in my first message. I'm sure > > some people on the mailing list have small mailboxes, so I didn't want to > > spam everyone with a 3MB attachment. These are the URLs from my original > > post: > > http://rsyslog-users.1305293.n2.nabble.com/file/n7591426/rsyslog.conf > > http://rsyslog-users.1305293.n2.nabble.com/file/n7591426/gdb.txt > > > > If they're still not working for you, just let me know and I'll find another > > way to send them. > > > > Thanks. > > > > > > > > -- > > View this message in context: http://rsyslog-users.1305293.n2.nabble.com/Segementation-Fault-when-Rsyslog-Starts-tp7591426p7591437.html > > Sent from the rsyslog-users mailing list archive at Nabble.com. > > _______________________________________________ > > 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. > > > > -- > Regards, > Janmejay > http://codehunk.wordpress.com > _______________________________________________ > 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.
