Hi, I noticed that my build cluster was no longer able to build rsyslog without any changes to rsyslog itself (i.e. builds which passed are now failing).
Looks like a problem with the current jemalloc release. I filed a bug report upstream: https://github.com/jemalloc/jemalloc/issues/430 <=jemalloc-4.1.0 works fine. I am only hitting this when running as non-root user. rsyslog techbench itself only logged the timeout, i.e. > =============================================================================== > [stop-localvar.sh]: testing stop statement together with local variables > ------------------------------------------------------------ > Test: ./stop-localvar.sh > ------------------------------------------------------------ > ABORT! Timeout waiting on startup (pid file) > FAIL stop-localvar.sh (exit status: 1) > > FAIL: stop-msgvar.sh > ==================== Same when running with valgrind. A strace log file is attached to upstream's bug report. If anybody has an idea how to get a more meaningful output for a better error report... -- Regards, Thomas
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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.
