Hi, Unfortunately, the omelasticsearch module doesn't load for me. All the others, like mmjsonparse, *relp and imptcp seem fine, but this one says:
rsyslogd: could not load module '/usr/lib/rsyslog/omelasticsearch.so', dlopen: /usr/lib/rsyslog/omelasticsearch.so: undefined symbol: pow I'm attaching a test conf and a debug log. Should I move this to another thread, private Emails or bugzilla? Best regards, Radu 2012/12/7 Radu Gheorghe <[email protected]> > Thank you very much Andre! I will test it and report the results. > > Sorry for the delay in replying, I was hoping to come back with the > feedback directly, but something has come up and my tests will be delayed > for a while. > > Best regards, > Radu > > > 2012/12/6 Andre Lorbach <[email protected]> > >> Hi, >> >> thanks for sending me your changed files. I merged them into my build >> system and updated our Ubuntu Packages to "rsyslog_7.3.4-1adiscon2". >> Maybe you can run some tests with the new packages >> (rsyslog-elasticsearch, rsyslog-imptcp, rsyslog-mmjsonparse and >> rsyslog-mongodb) on your system using the Adiscon Ubuntu Repository? >> >> Best regards, >> Andre Lorbach >> >> > -----Original Message----- >> > From: [email protected] [mailto:rsyslog- >> > [email protected]] On Behalf Of Radu Gheorghe >> > Sent: Mittwoch, 5. Dezember 2012 16:28 >> > To: rsyslog-users >> > Subject: Re: [rsyslog] Ubuntu 12 (Precise) v7-devel packages >> > >> > Hi, >> > >> > As you might have figured, we need Ubuntu packages as well. Especially >> for >> > Precise. >> > >> > The main question I have is where to contribute, and are contributions >> > needed? I think it would be nice to join forces somehow, for making >> recent >> > rsyslog packages available. >> > >> > To be more specific, we need rsyslog and rsyslog-relp, with >> omelasticsearch, >> > imptcp and mmjsonparse on top of them. So I took the source package from >> > Todd's PPA (I hope you don't mind, Todd!), and from it I've built: >> > - rsyslog-elasticsearch >> > - rsyslog-imptcp >> > - rsyslog-mmjsonparse >> > >> > I also did a minor fix by taking out the "-c5" parameter from >> /etc/default and >> > the init script. All in all it seems to work fine - although there's >> quite some >> > more work ahead, like making it available for 32-bit and for other >> versions of >> > Ubuntu. >> > >> > Now to put the question into context, for me (and others interested in >> the >> > components mentioned above), I see the following options of publishing >> the >> > packages I've done: >> > 1. my own PPA/repo >> > 2. Adiscon's repo. Or PPA if you guys want to make one 3. Todd's PPA 4. >> > Debian Experimental repo >> > >> > Of course that, except for option 1, the maintainers would have to >> agree first >> > :) >> > >> > What do you think or suggest? >> > >> > Best regards, >> > Radu >> > >> > 2012/12/1 Andre Lorbach <[email protected]> >> > >> > > > thanks for that effort. Without having had a closer look at the >> > > > package >> > > itself, I >> > > > just wondered if you based it on the latest Ubuntu or Debian >> package? >> > > >> > > It is based on the latest Ubuntu RSyslog package I could install on >> > > Ubuntu 12.04. >> > > What I basically did was taking the package source, modifying, adding >> > > and updating dependencies like libee, libestr, librelp. >> > > Then I created a local repository using mini-dinstall and dput, and >> > > added all these packages to it. >> > > After initially and successful testing, I uploaded the local >> > > repository to our webserver. >> > > >> > > > Also, an observation while skimming through the repo: The 0ubuntu? >> > > > versioning scheme is usually reserved for official Ubuntu packages. >> > > > You could use 0adisconX or something like that. This would have the >> > > > additional benefit, that once there is an official Ubuntu package >> > > available, it >> > > > would supersede your version as XXX-0ubuntuX > XXX-0adisconX >> > > >> > > Thanks for the hint, I wasn't aware of this versioning fact. Your >> > > recommendation sounds reasonable, I will change this with the next >> > > package update. >> > > >> > > Best regards, >> > > Andre Lorbach >> > > _______________________________________________ >> > > 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.conf
Description: Binary data
rsyslog_debug.log
Description: Binary data
_______________________________________________ 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.
