Current rsyslog should *not* drag in any librdkafka package at all. The one in the repository is meant only for older releases. So you should not have any conflict in the first place. That's what I have requested and been told it is.
Rainer Sent from phone, thus brief. Derek DiFilippo <de...@jsonar.com> schrieb am Mi., 18. Apr. 2018, 22:16: > Hi Rainer, Hi Florian: > > I have read Florian's replies (thank you) but I don't get the connection > between those replies and what I see as the main issue: > We have two rdkafka packages, one from rsyslog and one from epel, trying to > provide the same shared object file. > > BTW, I am running this install procedure on a clean AWS RHEL 7.x instances. > No older version of rsyslog other than what comes with RedHat. > > -D. > > On Wed, Apr 18, 2018 at 1:08 PM, Rainer Gerhards <rgerha...@hq.adiscon.com > > > wrote: > > > Derek, > > > > Thanks for the explanation. I do not fully understand it, but I guess > > Florian and Andre will. > > > > But what I know is that current rsyslog should not require any librdkafka > > version whatsoever, because it should be linked in statically, and so the > > rsyslog binary should contain all the code. > > > > We do this because librdkafka has some serious bugs which are only fixed > in > > the very latest version. > > > > Rainer > > > > Sent from phone, thus brief. > > > > Derek DiFilippo <de...@jsonar.com> schrieb am Mi., 18. Apr. 2018, 20:32: > > > > > Rainier, > > > > > > On the contrary, we do not pin our rsyslog version. We adopt your > > releases > > > as soon as they are available (subject to our internal CI system). > > > > > > What's changed here is that one of our products recently brought in > > > librdkafka as a dynamic dependency. > > > > > > $ rpm -qpR sonarw.2.2-gabcd123.jsonar.x86_64 | grep librdkafka ## older > > > version sonarw 2.2 > > > # .... nothing.... > > > $ rpm -qpR sonarw.2.3-g1234abc.jsonar.x86_64 | grep librdkafka ## > latest > > > version sonarw 2.3 > > > librdkafka++.so.1()(64bit) > > > librdkafka.so.1()(64bit) > > > > > > Before we do a yum install, we add the rsyslog repo (and ours, and > > others) > > > to the /etc/yum.repos.d on the target machine. > > > When yum installs our top level package suite: > > > + sonarw brings in librdkafka from epel > > > + rsyslog brings in librdkafka1 from your repo > > > ... and there's a conflict as shown in my original email in this > thread. > > > > > > There's no opportunity to "delete" the librdkafka1 package from the > > rsyslog > > > repo. > > > Maybe there's some yum-foo I am unaware of (would priority fix this?) > to > > > resolve the conflict? > > > But I think that misses the point and is a workaround to be avoided. > > > > > > Note: we will end up building librdkafka from source and linking > > statically > > > as a CMake external project to reduce our dependency pressure. > > > As a result, I didn't want to linger on this. But since we're here --- > I > > > don't understand Florian's "it won't work if we remove it from the > > rsyslog > > > repo" reply. > > > And there's no "deleting" a package that never gets installed because > of > > a > > > conflict. > > > > > > Based on the rsyslog repo (it says epel-7 in the path...), why wouldn't > > you > > > use the librdkafka from epel as we do? > > > If you need to pin a version you should specify that when you build the > > > rpm, not by putting that particular package in your repo. > > > > > > I'm sure everyone *knows* this (not trying to be patronizing) so -- why > > is > > > librdkafka1 there? > > > Maybe the older rsyslog rpms were built without specifying a librdkafka > > > version and newer versions of librdkafka broke older rsyslog releases? > > > > > > Thanks everyone for reading through all of this! > > > > > > -Derek. > > > > > > On Wed, Apr 18, 2018 at 10:52 AM, Rainer Gerhards < > > > rgerha...@hq.adiscon.com> > > > wrote: > > > > > > > Derek, > > > > > > > > I don't understand the issue here: do you intend to keep an outdated > > > > rsyslog version? With the current ones, no issue should exist, and if > > it > > > > does, we should fix it. > > > > > > > > So I am very interested to understand your issue. > > > > > > > > Rainer > > > > > > > > Sent from phone, thus brief. > > > > > > > > Derek DiFilippo <de...@jsonar.com> schrieb am Mi., 18. Apr. 2018, > > 19:24: > > > > > > > > > Hi Florian, > > > > > > > > > > Yes, that was a bit aggressive/silly of me to ask for it to be > > > removed... > > > > > > > > > > We're going to build from source and link statically to remove the > > > > > dependency/conflict. Deleting the rpm from the affected machine > won't > > > fix > > > > > the install conflict. > > > > > > > > > > Thanks everyone for the rapid replies, much appreciated. > > > > > > > > > > best, > > > > > -Derek > > > > > > > > > > On Wed, Apr 18, 2018 at 8:59 AM, Florian Riedl <fri...@adiscon.com > > > > > > wrote: > > > > > > > > > > > Derek, we cannot simply delete this from the repository. It is > > still > > > > > > needed for older versions or they won't be usable anymore. > > > > > > > > > > > > But, it should be sufficient to delete the librdkafka1 RPM from > the > > > > > > affected machine manually. > > > > > > > > > > > > Florian > > > > > > > > > > > > 2018-04-17 18:26 GMT+02:00 Derek DiFilippo <de...@jsonar.com>: > > > > > > > If it is statically linked, can librdkafka1 be removed from the > > > > > > repository? > > > > > > > It's quite an old version of the library. It should be > sufficient > > > to > > > > > use > > > > > > > the one from epel, correct? > > > > > > > > > > > > > > That would fix our conflict. > > > > > > > > > > > > > > Thanks, > > > > > > > -D. > > > > > > > > > > > > > > > > > > > > > On Tue, Apr 17, 2018, 01:05 Andre Lorbach < > alorb...@adiscon.com> > > > > > wrote: > > > > > > > > > > > > > >> It should be statically linked. > > > > > > >> Maybe the dependencies are not completely removed everywhere? > > > > > > >> > > > > > > >> Florian can you check please if the package scripts are using > > > > > > >> --enable-kafka-static properly? > > > > > > >> > > > > > > >> The adisconbuild-librdkafka packages are used for building > only, > > > and > > > > > we > > > > > > >> need them to get the static builds running on Launchpad! > > > > > > >> > > > > > > >> Best regards, > > > > > > >> Andre Lorbach > > > > > > >> > > > > > > >> > -----Original Message----- > > > > > > >> > From: rsyslog [mailto:rsyslog-boun...@lists.adiscon.com] On > > > > Behalf > > > > > Of > > > > > > >> > Rainer Gerhards > > > > > > >> > Sent: Monday, April 16, 2018 8:26 PM > > > > > > >> > To: rsyslog-users <rsyslog@lists.adiscon.com> > > > > > > >> > Subject: Re: [rsyslog] librdkafka packages in > > > > > > >> v8-stable/epel-7/x86_64/RPMS > > > > > > >> > > > > > > > >> > Mmmhhhh... I was told that we link statically to librdkafka, > > so > > > > > there > > > > > > >> should > > > > > > >> > no kafka package at all be installed (actually this was > what I > > > > asked > > > > > > >> for). > > > > > > >> > > > > > > > >> > @florian, @andre can you comment? > > > > > > >> > > > > > > > >> > Rainer > > > > > > >> > > > > > > > >> > Sent from phone, thus brief. > > > > > > >> > > > > > > > >> > Derek DiFilippo <de...@jsonar.com> schrieb am Mo., 16. Apr. > > > 2018, > > > > > > 20:19: > > > > > > >> > > > > > > > >> > > Hi Rainer, hi everyone, > > > > > > >> > > > > > > > > >> > > In addition to a dependency on rsyslog, one of our > packages > > > now > > > > > > >> > > depends on librdkafka and librdkafka-devel. > > > > > > >> > > > > > > > > >> > > We want to use the librdkafka packages provided by epel, > > > nothing > > > > > > >> fancy. > > > > > > >> > > > > > > > > >> > > I'm seeing a conflict between the librdkafka1 package in > the > > > > > rsyslog > > > > > > >> > > repo (note the "1" at the end of the library name) and the > > > ones > > > > > > >> > > provided by epel. > > > > > > >> > > > > > > > > >> > > ... > > > > > > >> > > ... > > > > > > >> > > librdkafka x86_64 0.11.3-1.el7 epel > > > > > > >> > > 326 k > > > > > > >> > > librdkafka-devel x86_64 0.11.3-1.el7 epel > > > > > > >> > > 43 k > > > > > > >> > > librdkafka1 x86_64 0.8.5-0 rsyslog_v8 > > > > > > >> > > 100 k > > > > > > >> > > ... > > > > > > >> > > ... > > > > > > >> > > > > > > > > >> > > Transaction check error: > > > > > > >> > > file /usr/lib64/librdkafka++.so.1 conflicts between > > > attempted > > > > > > >> > > installs of > > > > > > >> > > librdkafka1-0.8.5-0.x86_64 and > > librdkafka-0.11.3-1.el7.x86_64 > > > > > > >> > > file /usr/lib64/librdkafka.so.1 conflicts between > > attempted > > > > > > installs > > > > > > >> > > of > > > > > > >> > > librdkafka1-0.8.5-0.x86_64 and > > librdkafka-0.11.3-1.el7.x86_64 > > > > > > >> > > > > > > > > >> > > Can librdkafka1 be removed from the rsyslog repo? What is > > the > > > > > > >> > > rationale for pinning a version of librdkafka via the > > > > librdkafka1 > > > > > > >> package? > > > > > > >> > > > > > > > > >> > > If librdkafka1 must stay in the rsyslog repo what do you > > > > recommend > > > > > > as > > > > > > >> > > the best practice for resolving this conflict? > > > > > > >> > > > > > > > > >> > > I see a lot of "adisconbuild-librdkafka*" packages in the > > > repo. > > > > > Why > > > > > > >> > > are they there? Is the solution to change the dependency > in > > > > *our* > > > > > > >> > > package form librdkafka to adiscon-librdkafka? I might be > > > > > > comfortable > > > > > > >> > > with that if I know why the adiscon packages are there. > > > > > > >> > > > > > > > > >> > > As a fallback we could add librdkafka as an external > project > > > via > > > > > > CMake > > > > > > >> > > and build from source but I wanted to check in here first > > > before > > > > > > >> > proceeding. > > > > > > >> > > > > > > > > >> > > Apologies if I missed something obvious. I did my best > > > googling > > > > > > >> > > due-diligence and couldn't find anyhing satisfactory. > > > > > > >> > > > > > > > > >> > > Thanks for your time & patience! > > > > > > >> > > _______________________________________________ > > > > > > >> > > 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. > > > > > > >> _______________________________________________ > > > > > > >> 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. > > > > > > _______________________________________________ > > > > > > 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. > > > > > > > > > _______________________________________________ > > > > 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. > > > > > _______________________________________________ > > 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. > _______________________________________________ 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.
