https://bugzilla.balabit.com/show_bug.cgi?id=226 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu AssignedTo|bazsi@balabit.hu |algernon@balabit.hu --- Comment #1 from Gergely Nagy <algernon@balabit.hu> 2013-03-08 14:21:20 --- This is interesting, because this issue is supposed to be fixed in 3.3.8 (it was present in 3.3.7). Can you post an strace of syslog-ng -Fvde ? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

https://bugzilla.balabit.com/show_bug.cgi?id=226 --- Comment #3 from Gergely Nagy <algernon@balabit.hu> 2013-04-12 12:47:45 --- I can't reproduce this with a clean 3.3.8 install on Fedora 19 (glibc 2.17). An strace would be helpful... Which distribution are you using, by the way? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

https://bugzilla.balabit.com/show_bug.cgi?id=226 --- Comment #5 from Fabien Wernli <bugzilla.balabit@faxm0dem.org> 2013-08-08 12:42:30 --- (From update of attachment 80) I just built syslog-ng 3.3.11 from source on a RHEL6 and it works fine. However, when building a 3.4.2, and running the dameon I get the exact same error: iv_tls_user_register: called after iv_init I attached the strace -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

https://bugzilla.balabit.com/show_bug.cgi?id=226 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bazsi@balabit.hu |algernon@balabit.hu --- Comment #6 from Gergely Nagy <algernon@balabit.hu> 2013-08-11 15:05:22 --- I think I finally understand what is happening. If you look at the strace, the dynamic linker will try to open libsyslog-ng-3.4.2.so first, and will fail with the assert when it later tries libsyslog-ng-3.3.11.so. Both of them link to ivykis, but different versions, and that's the cause of the problem. How would that happen? Well, if syslog-ng is installed into /usr, libsyslog-ng.so will go into /usr/lib, which is on the default linker path. Every time you do a -lsyslog-ng, it will then link to that. So if you have 3.4 installed, and compile 3.3, it will still link modules to 3.4. The easiest way around this is to use a libdir at configure-time that's not on the linker path, like /usr/lib/syslog-ng. I'm considering changing syslog-ng's build system to put libsyslog-ng into a private directory instead, to avoid this kind of confusion. I won't do that for 3.3, nor 3.4, that would be an invasive change, and it's easier to document this there instead. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

https://bugzilla.balabit.com/show_bug.cgi?id=226 --- Comment #7 from Fabien Wernli <bugzilla.balabit@faxm0dem.org> 2013-08-12 08:49:57 --- I can confirm that this error message disappears when first cleaning up the 3.3.x installation before running the 3.4.y Thanks -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.