On 12/21/2017 1:10 PM, Andrew Akins via rsyslog wrote: > I was wondering if anyone had seen this. I’m running rsyslog on Alpine Linux, > deployed as a container. Rsyslog was built from source, and is version 8.31.0 > > Basically, initialization of a omkafka message is failing: > > 2648.027688868:imuxsock.c : imuxsock.c: --------imuxsock calling select, > active file descriptors (max 0): 0 > 2648.027702811:main Q:Reg/w0 : ruleset.c: processBATCH: batch of 1 elements > must be processed > 2648.027707648:main Q:Reg/w0 : ruleset.c: processBATCH: next msg 0: <46>Dec > 21 18:57:28 rsyslogd: [origin software="rsyslogd" swVersion="8.31.0" > x-pid="98" x-info="http://www.rsyslog.com";] start > 2648.027713441:main Q:Reg/w0 : rainerscript.c: ACTION 0 > [builtin:omfile:action(type="builtin:omfile" ...)] > 2648.027721223:main Q:Reg/w0 : ruleset.c: executing action 0 > 2648.027727363:main Q:Reg/w0 : ../action.c: action 'action 0': called, > logging to builtin:omfile (susp 0/0, direct q 1) > 2648.027752262:main Q:Reg/w0 : ../action.c: action 'action 0': is > transactional - executing in commit phase > 2648.027757035:main Q:Reg/w0 : ../action.c: wti 0x560e9b6ecdc0: we need to > create a new action worker instance for action 0 > 2648.027762040:main Q:Reg/w0 : ../action.c: wti 0x560e9b6ecdc0: created > action worker instance 1 for action 0 > 2648.027765893:main Q:Reg/w0 : ../action.c: action[action 0] transitioned to > state: itx > 2648.027769331:main Q:Reg/w0 : ../action.c: action 'action 0': set suspended > state to 0 > 2648.027772205:main Q:Reg/w0 : rainerscript.c: ACTION 1 > [omkafka:action(type="omkafka" ...)] > 2648.027779532:main Q:Reg/w0 : ruleset.c: executing action 1 > 2648.027783450:main Q:Reg/w0 : ../action.c: action 'action 1': called, > logging to omkafka (susp 0/0, direct q 1) > 2648.027794309:main Q:Reg/w0 : ../action.c: wti 0x560e9b6ecdc0: we need to > create a new action worker instance for action 1 > 2648.027801169:main Q:Reg/w0 : ../action.c: wti 0x560e9b6ecdc0: created > action worker instance 1 for action 1 > 2648.027804591:main Q:Reg/w0 : ../action.c: action[action 1] transitioned to > state: itx > 2648.027808121:main Q:Reg/w0 : ../action.c: entering actionCalldoAction(), > state: itx, actionNbr 1 > 2648.027848119:main Q:Reg/w0 : omkafka.c: omkafka: setting custom > configuration parameter: log_level:7 > 2648.027854623:main Q:Reg/w0 : omkafka.c: omkafka: setting custom > configuration parameter: debug:broker,topic,msg > 2648.030213741:main Q:Reg/w0 : errmsg.c: Called LogMsg, msg: omkafka: error > creating kafka handle: Failed to create thread: (null) (0) > > 2648.030228821:main Q:Reg/w0 : iminternal.c: signaling new internal message > via SIGTTOU: 'omkafka: error creating kafka handle: Failed to create thread: > (null) (0) [v8.31.0 try http://www.rsyslog.com/e/2422]' > 2648.030246764:main Q:Reg/w0 : omkafka.c: omkafka: doAction failed with > status -2422 > 2648.030252261:main thread : janitor.c: janitorRun() called > 2648.030261582:main Q:Reg/w0 : errmsg.c: Called LogMsg, msg: action 'action > 1' (module 'omkafka') message lost, could not be processed. Check for > additional error messages before this one. > > > Any thoughts on what it could be, or done strategies on debugging or tracking > it down?
I did a brief search in the GitHub issue tracker and didn't get any hits, but that could just be the search string I used. Either way, I recommend opening up an issue there, posting what you have included here and providing a sample configuration that can be used to replicate the error. _______________________________________________ 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.
