Hello Gary, Hello rsyslog-users,
I got exactly the same issue :
- With czmq 1.3.2, rsyslog cannot dlopen omzmq3; because the
zsys_handler_set symbol is missing.
- With czmq 1.4.1 (1.5.1 does not exists), it segfaults !
Here is the backtrace :
(gdb) bt
#0 0x00007ffff6c3f975 in vfprintf () from /lib64/libc.so.6
#1 0x00007ffff6c67c52 in vsnprintf () from /lib64/libc.so.6
#2 0x00007ffff55815ad in s_send_string () from
/opt/infra/local/lib/libczmq.so.1
#3 0x00007ffff5581941 in zstr_send () from
/opt/infra/local/lib/libczmq.so.1
#4 0x00007ffff5789c56 in writeZMQ (
msg=0x7fffec00bf70 "<190>2013-08-01T15:37:12.849270+02:00 10.67.10.7
squid[29471]: 10.xx.xx.x - - [01/Aug/2013:15:37:12 +0200] \"GET
http://www.google.com/ads/user-lists/xxxxxxxxxx/?label=xxxxxxxxxxxxxxxxxxx&fmt=1&num=2&c
"...,
pData=0x6bcb90) at omzmq3.c:266
#5 0x00007ffff5789f0e in doAction (ppString=0x6c3388, iMsgOpts=32,
pData=0x6bcb90) at omzmq3.c:339
#6 0x000000000045c844 in actionCallDoAction (pThis=0x6bc8b0,
pMsg=0x7fffe8015100, actParams=0x6c3388) at ../action.c:918
#7 0x000000000045c97a in actionProcessMessage (pThis=0x6bc8b0,
pMsg=0x7fffe8015100, actParams=0x6c3388, pbShutdownImmediate=0x6ac5c8) at
../action.c:967
#8 0x000000000045cc48 in tryDoAction (pAction=0x6bc8b0, pBatch=0x6ac558,
pnElem=0x7ffff373f86c) at ../action.c:1061
#9 0x000000000045ce3b in submitBatch (pAction=0x6bc8b0, pBatch=0x6ac558,
nElem=32) at ../action.c:1128
#10 0x000000000045d23d in processAction (pAction=0x6bc8b0, pBatch=0x6ac558)
at ../action.c:1253
#11 0x000000000045d37f in processBatchMain (pAction=0x6bc8b0,
pBatch=0x6ac558, pbShutdownImmediate=0x0) at ../action.c:1291
#12 0x000000000045090d in qqueueEnqObjDirectBatch (pThis=0x6bdfe0,
pBatch=0x6ac558) at queue.c:994
#13 0x000000000045e09b in doQueueEnqObjDirectBatch (pAction=0x6bc8b0,
pBatch=0x6ac558) at ../action.c:1655
#14 0x000000000045e13f in doSubmitToActionQBatch (pAction=0x6bc8b0,
pBatch=0x6ac558) at ../action.c:1677
#15 0x000000000045dde9 in doSubmitToActionQNotAllMarkBatch
(pAction=0x6bc8b0, pBatch=0x6ac558) at ../action.c:1591
#16 0x000000000045542f in execAct (stmt=0x6bc6e0, pBatch=0x6ac558,
active=0x0) at ruleset.c:234
#17 0x00000000004560a7 in scriptExec (root=0x6b5ea0, pBatch=0x6ac558,
active=0x0) at ruleset.c:529
#18 0x0000000000456217 in processBatch (pBatch=0x6ac558) at ruleset.c:578
#19 0x000000000040defd in msgConsumer (notNeeded=0x0, pBatch=0x6ac558,
pbShutdownImmediate=0x6ac5c8) at syslogd.c:569
#20 0x000000000045204f in ConsumerReg (pThis=0x6ac5b0, pWti=0x6ac530) at
queue.c:1858
#21 0x000000000044e48c in wtiWorker (pThis=0x6ac530) at wti.c:313
#22 0x000000000044d692 in wtpWorker (arg=0x6ac530) at wtp.c:388
#23 0x00007ffff79b1851 in start_thread () from /lib64/libpthread.so.0
#24 0x00007ffff6ce067d in clone () from /lib64/libc.so.6
And that's valgrind's feedback :
==18139== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==18139== Access not within mapped region at address 0xDAFD3444
==18139== at 0x5CC5975: vfprintf (in /lib64/libc-2.12.so)
==18139== by 0x5CEDC51: vsnprintf (in /lib64/libc-2.12.so)
==18139== by 0x78945AC: s_send_string (in
/opt/infra/local/lib/libczmq.so.1.0.0)
==18139== by 0x7894940: zstr_send (in
/opt/infra/local/lib/libczmq.so.1.0.0)
==18139== by 0x767FC55: writeZMQ (omzmq3.c:266)
==18139== by 0x767FF0D: doAction (omzmq3.c:339)
==18139== by 0x45C843: actionCallDoAction (action.c:918)
==18139== by 0x45C979: actionProcessMessage (action.c:967)
==18139== by 0x45CC47: tryDoAction (action.c:1061)
==18139== by 0x45CE3A: submitBatch (action.c:1128)
==18139== by 0x45D23C: processAction (action.c:1253)
==18139== by 0x45D37E: processBatchMain (action.c:1291)
I suspect the "Access not within mapped region" to be related with our
issue. ;-)
This is the only commit which modified omzmq3 :
http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=92e55a8b1b20bedd82a81220a6173bd761f29ddd
The commit updated the README to explicitely tell us we should use czmq
1.3.2. But that looks wrong (missing symbol issue).
Brian, Hongfei: any thoughts on the issue ?
Thanks a lot !
Philippe Muller
On Tue, Jul 23, 2013 at 12:09 AM, Gary Foster <[email protected]>wrote:
> We recently upgraded to the latest 7.4.2 stable release (and have been
> tracking the 7x-devel branch fairly closely prior to that). However, with
> this upgrade I lost the ability to use the omzmq3 plugin.
>
> Using zeromq 3.2.3 and libczmq 1.3.2 I get this when I try to load the
> omzmq3 plugin:
>
> "undefined symbol: zsys_handler_set"
>
> upgrading to libczmq 1.5.1 allows me to properly load the module, but any
> time I try to actually emit a message on the bus it then segfaults.
>
> Has anyone else encountered this?
>
> -- Gary F.
>
> _______________________________________________
> 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.
