Hi, My repositories came directly from adiscon repo (just a mirror).
So to sort it out: 1) Who can I spend a beer to get also daily RPM packages? ;) In production area you won't want to compile everything daily again, and Migration from 8.16 --> 8.18 leads for me to a broken situtation (liblognorm+rsys-module +json vs rsyslog+libfastjson) 2) Why doesn't we provide a 1.4 Version of liblognorm using the pre-2.0 Version? 3) The issue was that the Adiscon provided RPM for mmlognorm requires json-c. 4) Is a compatibility between json-c and libfastjson in the future planned (as other SW stick on json-c). Sorry I don't want to waste your time with my questions, but for me the direction is not very clear. Thank you, regards Chris 2016-04-21 10:20 GMT+02:00 David Lang <[email protected]>: > On Thu, 21 Apr 2016, Rainer Gerhards wrote: > >> 2016-04-21 10:13 GMT+02:00 David Lang <[email protected]>: >>> >>> On Thu, 21 Apr 2016, Christopher Racky wrote: >>> >>>> Hi, >>>> Thanks a lot so far. >>>> David you assumed right. I was not able to get a coredump as only one >>>> thread dies. >>>> I noticed, that on my RHEL 6.7 System I have json-c AND libfastjson >>>> installed in parallel. >>>> As far as I read this is a bad idear and could lead into issues). >>>> >>>> Removing it leads to new issues: >>>> a) The latest released Version of liblognorm 1.3 depends on json-c, so >>>> how should only libfastjson work? >>>> b) rsyslog-mmnormalize module seems depends also on json-c !?? >>>> c) some other components (not from rsyslog universe) depend also on >>>> json-c >>>> >>>> Comments? >>> >>> >>> >>> you need to have liblognorm, mmnormalize and rsyslog all using the same >>> library. I've been compiling my own for the last several months as I've >>> been >>> fighting through the segfault issues (and using the liblognorm 2.0 >>> features) >>> >>> make sure that the packages that you have are all ones from the adiscon >>> repo >>> (no stray packages with the same name/version from redhat repos) >>> >> >> This is one of the things now held by the other discussion ;) There >> currently is not real clean way. I need to get 0.99.3 out... which >> means I need to clean up all packaging issues plus some code things, >> which means I need... I guess you get the idea why I say "there is >> lots of important things to do". >> >> Best bet is the daily build repo, this is pretty cleaned up now. > > > Yeah, I just had some fun trying to compile things were some things were > looking for liblognorm1.so.4 insead of .10 and it turned out that in my > build environment I had liblognorm1_2.0.0.2016... as well as > liblognorm1_2.0.0~2016... and the build was pulling in the wrong one. > > we timed the name change to hit with a rsyslog release, but when not all the > packages rev at the same time there is no seamless way to fix the names. Now > I understand the comment about needing to clear out old versions of things > :-( > > > David Lang > _______________________________________________ > 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.
