Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 21:06, Michael Biebl wrote: Am 05.03.2014 20:14, schrieb Daniel Pocock: On 05/03/14 19:58, Michael Biebl wrote: Michael, if Rainer confirms the fix version for the template issue, would you mind updating the packages and then just ping me to test? Sure, no problem. I'm currently waiting for liblogging to pass the NEW queue so I can upload rsyslog 7.6.0. I expect in that case the fix will land in 7.6.1 and I would then just update to that version. Michael Here are some upstream patches you could cherry-pick into the package: 18eaa5cc5c325e1f4c531dd03b463997c7fde1b4 (template not mandatory) 9d0fc675a51125acde057d0e53e8323c5e1ed572 (fix a string termination bug) This got it working for me I create the debian/patches on a branch in collab-maint, my branch is called pocock Please feel free to merge and release as 7.4.4-2, this will let people test while waiting for the 7.6.x releases -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 06/03/14 10:10, Daniel Pocock wrote: On 05/03/14 21:06, Michael Biebl wrote: Am 05.03.2014 20:14, schrieb Daniel Pocock: On 05/03/14 19:58, Michael Biebl wrote: Michael, if Rainer confirms the fix version for the template issue, would you mind updating the packages and then just ping me to test? Sure, no problem. I'm currently waiting for liblogging to pass the NEW queue so I can upload rsyslog 7.6.0. I expect in that case the fix will land in 7.6.1 and I would then just update to that version. Michael Here are some upstream patches you could cherry-pick into the package: 18eaa5cc5c325e1f4c531dd03b463997c7fde1b4 (template not mandatory) 9d0fc675a51125acde057d0e53e8323c5e1ed572 (fix a string termination bug) This got it working for me I create the debian/patches on a branch in collab-maint, my branch is called pocock Please feel free to merge and release as 7.4.4-2, this will let people test while waiting for the 7.6.x releases Just confirming that after those patches, LogAnalyzer 3.6.5 works for me now too In the LogAnalyzer install.php, I select SourceType: MongoDB native Select View: Syslog Fields Table type: MongoDB Database Host: localhost Database name: logs Database tablename: syslog Database user: (delete the default, must be blank) Database password: (also blank) This is how it appears in config.php: $CFG['DefaultSourceID'] = 'Source1'; $CFG['Sources']['Source1']['ID'] = 'Source1'; $CFG['Sources']['Source1']['Name'] = 'My Syslog Source'; $CFG['Sources']['Source1']['ViewID'] = 'SYSLOG'; $CFG['Sources']['Source1']['SourceType'] = SOURCE_MONGODB; $CFG['Sources']['Source1']['DBTableType'] = 'mongodb'; $CFG['Sources']['Source1']['DBServer'] = 'localhost'; $CFG['Sources']['Source1']['DBName'] = 'logs'; $CFG['Sources']['Source1']['DBUser'] = ''; $CFG['Sources']['Source1']['DBPassword'] = ''; $CFG['Sources']['Source1']['DBTableName'] = 'syslog'; In /etc/rsyslog.conf there is just this: $ModLoad ommongodb *.*action(type=ommongodb server=127.0.0.1 db=logs collection=syslog) No need to specify template or anything else. The values db=logs and collection=syslog come from the article here: http://loganalyzer.adiscon.com/articles/using-mongodb-with-rsyslog-and-loganalyzer/ I've suggested to upstream that the ommongodb defaults and the article and LogAnalyzer defaults for db and collection names should all be synchronized https://github.com/rsyslog/loganalyzer/issues/4 Once that is done, the README.Debian will probably be OK as it is again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
Am 06.03.2014 10:31, schrieb Daniel Pocock: On 06/03/14 10:10, Daniel Pocock wrote: On 05/03/14 21:06, Michael Biebl wrote: Am 05.03.2014 20:14, schrieb Daniel Pocock: On 05/03/14 19:58, Michael Biebl wrote: Michael, if Rainer confirms the fix version for the template issue, would you mind updating the packages and then just ping me to test? Sure, no problem. I'm currently waiting for liblogging to pass the NEW queue so I can upload rsyslog 7.6.0. I expect in that case the fix will land in 7.6.1 and I would then just update to that version. Michael Here are some upstream patches you could cherry-pick into the package: 18eaa5cc5c325e1f4c531dd03b463997c7fde1b4 (template not mandatory) 9d0fc675a51125acde057d0e53e8323c5e1ed572 (fix a string termination bug) This got it working for me Ok, thanks a lot for doing all this testing. Should liblogging not be accepted within the next couple of days, I'll release a 7.4.4-2. Luca, maybe you can have a look at liblogging in NEW to speed this up a little. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
2014-03-06 10:41 GMT+01:00 Michael Biebl bi...@debian.org: Luca, maybe you can have a look at liblogging in NEW to speed this up a little. I've just marked it for acceptance. Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself LogAnalyzer and rsyslog are from the same upstream too, so I would be surprised if they would not have them working together I had a look at the Git history for the ommongodb, does anything stand out here? https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb You state the problem started with 7.4.0-1 - could you comment on the previous set of versions that you had working (both rsyslog and LogAnalyzer versions)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
[dropping debian-devel] Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself LogAnalyzer and rsyslog are from the same upstream too, so I would be surprised if they would not have them working together I had a look at the Git history for the ommongodb, does anything stand out here? https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb You state the problem started with 7.4.0-1 - could you comment on the previous set of versions that you had working (both rsyslog and LogAnalyzer versions)? If the README.Debian (which was based on [1]) is no longer correct, please let me know. If you are using the 7.4.0 backport for wheezy, make sure to also use the libjson-c 0.11 backport. [1] http://git.adiscon.com/?p=rsyslog.git;a=blob;f=plugins/ommongodb/README;hb=HEAD -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 11:26, Michael Biebl wrote: [dropping debian-devel] Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself LogAnalyzer and rsyslog are from the same upstream too, so I would be surprised if they would not have them working together I had a look at the Git history for the ommongodb, does anything stand out here? https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb You state the problem started with 7.4.0-1 - could you comment on the previous set of versions that you had working (both rsyslog and LogAnalyzer versions)? If the README.Debian (which was based on [1]) is no longer correct, please let me know. If you are using the 7.4.0 backport for wheezy, make sure to also use the libjson-c 0.11 backport. [1] http://git.adiscon.com/?p=rsyslog.git;a=blob;f=plugins/ommongodb/README;hb=HEAD Michael, thanks for the fast response on this In the bug report, it goes on to say that after correcting the first issue, I can dump data to mongodb again, though the format doesn't match previous entries. and then the email to debian-devel suggests that LogAnalyzer can no longer read the data (even though it is there) It is this latter issue that I am curious about - is it a deliberate schema change? Is it just the libjson-c version (and can you add that to the control file)? Does it require some newer version of LogAnalyzer (and is anyone aware if upstream is working on that, if it is unreleased, etc)? I also queried it upstream: https://github.com/rsyslog/rsyslog/issues/46 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
Am 05.03.2014 11:26, schrieb Michael Biebl: [dropping debian-devel] Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself Florian, have you followed the steps outlined in http://www.rsyslog.com/tag/ommongodb/ ? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
Hello all, On Wed, Mar 05, 2014 at 11:26:23AM +0100, Michael Biebl wrote: [...] If the README.Debian (which was based on [1]) is no longer correct, please let me know. Hmm, I thought I did exactly that: reporting a bug against rsyslog-mongodb, stating that the instruction [sic] from README.Debian don't seem to work at all. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721277#5 Cheers, Flo signature.asc Description: Digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On Wed, Mar 05, 2014 at 12:13:23PM +0100, Michael Biebl wrote: Am 05.03.2014 11:26, schrieb Michael Biebl: Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself Florian, have you followed the steps outlined in http://www.rsyslog.com/tag/ommongodb/ ? ITIYM http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ in particular? Not until now. Previously I followed http://www.rsyslog.com/doc/rsyslog_conf_modules.html/ommongodb.html (which now redirects to http://www.rsyslog.com/doc/ommongodb.html). I have now tried to implement the configuration mentioned there verbatim. This led to remote logs simply disappearing, i.e. not being logged on my syslog host. Thus I have reverted the change, for my current mongodb rsyslog configuration please see the other mail to Daniel. Cheers, Flo signature.asc Description: Digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 14:38, Florian Ernst wrote:
On Wed, Mar 05, 2014 at 12:13:23PM +0100, Michael Biebl wrote:
Am 05.03.2014 11:26, schrieb Michael Biebl:
Am 05.03.2014 11:07, schrieb Daniel Pocock:
On 05/03/14 09:09, Florian Ernst wrote:
On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote:
The rsyslog mongodb output module and the PHP mongodb modules are now in
wheezy-backports. This would appear to be sufficient to do something
like:
rsyslog = mongodb = loganalyzer
Has anybody else tried that or does anybody have any comments on it (or
recommended alternatives)?
That actually did work for a time, but something broke starting with
rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb
doesn't match what tools like loganalyzer expect, cf. #721277 / #728827.
As I was merely experimenting with it I didn't follow up any further.
Some of this looks like documentation bugs and/or problems with the
default config rather than mongodb integration itself
Florian, have you followed the steps outlined in
http://www.rsyslog.com/tag/ommongodb/ ?
ITIYM http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/
in particular?
Not until now. Previously I followed
http://www.rsyslog.com/doc/rsyslog_conf_modules.html/ommongodb.html
(which now redirects to http://www.rsyslog.com/doc/ommongodb.html).
I have now tried to implement the configuration mentioned there
verbatim. This led to remote logs simply disappearing, i.e. not being
logged on my syslog host. Thus I have reverted the change, for my
current mongodb rsyslog configuration please see the other mail to
Daniel.
Just out of interest, if you empty the database (or clear out the events
created before rsyslog 7.4 was installed) does LogAnalyzer work?
I'm not familiar with all the details of LogAnalyzer or the schema
attributes, this is just something that occurred to me when reading your
description of the problem
Also, I've just created a proper package of LogAnalyzer, it is in the
FTP queue - I'd appreciate any feedback you have about it or assistance
with maintaining it through our pkg-monitoring group. README.Debian has
some basic hints to get started with MongoDB, but if you could validate
or elaborate on it that would be very helpful.
While waiting for the package to be approved, you can build from git:
ssh://${USER}@git.debian.org/git/pkg-monitoring/loganalyzer.git
Vcs-Git: git://git.debian.org/pkg-monitoring/loganalyzer.git
Vcs-Browser:
http://git.debian.org/?p=pkg-monitoring/loganalyzer.git;a=summary
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On Wed, Mar 05, 2014 at 04:13:08PM +0100, Daniel Pocock wrote: On 05/03/14 14:38, Florian Ernst wrote: ITIYM http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ in particular? Not until now. Previously I followed http://www.rsyslog.com/doc/rsyslog_conf_modules.html/ommongodb.html (which now redirects to http://www.rsyslog.com/doc/ommongodb.html). I have now tried to implement the configuration mentioned there verbatim. This led to remote logs simply disappearing, i.e. not being logged on my syslog host. Thus I have reverted the change, for my current mongodb rsyslog configuration please see the other mail to Daniel. Following up to that: the config given in the first link looks like it should actually do the trick. It reads as if the missing parsing should take place. But as that config broke my remote syslog, I didn't tinker with it any further. It might be that there's a separate problem in my remote logging configuration, but I don't really see myself exploring that posiibility further at the moment, given that I lack a safe testing environment. Just out of interest, if you empty the database (or clear out the events created before rsyslog 7.4 was installed) does LogAnalyzer work? No. And I really wouldn't expect it to be working, given the flexible schema nature of mongodb. Also, I've just created a proper package of LogAnalyzer, it is in the FTP queue - I'd appreciate any feedback you have about it or assistance with maintaining it through our pkg-monitoring group. README.Debian has some basic hints to get started with MongoDB, but if you could validate or elaborate on it that would be very helpful. Tempting, but as I was merely toying with that, and in the light of a lack of spare time due to dayjob and family, I'm afraid there won't be much I'd manage to do. Cheers, Flo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 16:39, Florian Ernst wrote: On Wed, Mar 05, 2014 at 04:13:08PM +0100, Daniel Pocock wrote: On 05/03/14 14:38, Florian Ernst wrote: ITIYM http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ in particular? Not until now. Previously I followed http://www.rsyslog.com/doc/rsyslog_conf_modules.html/ommongodb.html (which now redirects to http://www.rsyslog.com/doc/ommongodb.html). I have now tried to implement the configuration mentioned there verbatim. This led to remote logs simply disappearing, i.e. not being logged on my syslog host. Thus I have reverted the change, for my current mongodb rsyslog configuration please see the other mail to Daniel. Following up to that: the config given in the first link looks like it should actually do the trick. It reads as if the missing parsing should take place. When you say first link, did you mean this one: http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ I had a look at that It basically appears that a) local log entries and entries defined on existing transports are not sent to mongodb using anything in that example b) log entries received over TCP port 13514 will be sent to mongodb, but only if they are in the CEE format (not just any syslog entry) But as that config broke my remote syslog, I didn't tinker with it any further. It might be that there's a separate problem in my remote logging configuration, but I don't really see myself exploring that posiibility further at the moment, given that I lack a safe testing environment. When you say broke your remote syslog, maybe your remote syslog is not sending to it with CEE format? I'm not sure that everybody will want to use the CEE format, many devices may only support regular syslog format, so a more basic example is needed too -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On Wed, Mar 05, 2014 at 07:11:57PM +0100, Daniel Pocock wrote: When you say first link, did you mean this one: http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ Yes. I had a look at that It basically appears that a) local log entries and entries defined on existing transports are not sent to mongodb using anything in that example Agreed. b) log entries received over TCP port 13514 will be sent to mongodb, but only if they are in the CEE format (not just any syslog entry) Agreed. When you say broke your remote syslog, maybe your remote syslog is not sending to it with CEE format? I guess so. I'm not familiar with the various formats, I was merely tinkering around. I'm not sure that everybody will want to use the CEE format, many devices may only support regular syslog format, so a more basic example is needed too Agreed. Cheers, Flo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
forwarded 721277 https://github.com/rsyslog/rsyslog/issues/46 thanks Thanks a lot for your interest so far! When I initially added rsyslog-mongodb I did some testing and based on that wrote README.Debian. I do not actively use it though, so I didn't follow the upstream changes for that module. Florian, from what I understand skimming over the bug report, the template parameter is no longer optional, and explicitly setting that makes ommongodb output data to the mongodb server again? If that is an intended change in behaviour or simply a bug, I dunno. If the former, we certainly would have to update README.Debian and it also warrants a NEWS.Debian. It should be possible in that case to come up with a template which outputs the data in the format as before. If it's simply a bug, that ommongodb no longer applies a default template, then we should fix that, of course. As said, I don't actively use the plugin, so any help regarding this is very much appreciated. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On Wed, Mar 05, 2014 at 07:58:50PM +0100, Michael Biebl wrote: Florian, from what I understand skimming over the bug report, the template parameter is no longer optional, and explicitly setting that makes ommongodb output data to the mongodb server again? Yes. This is what I reported and what is now also written in #740869. If that is an intended change in behaviour or simply a bug, I dunno. Neither do I, though upstream thinks this is/was a bug, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740869#10 Cheers, Flo signature.asc Description: Digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 19:58, Michael Biebl wrote: forwarded 721277 https://github.com/rsyslog/rsyslog/issues/46 thanks Thanks a lot for your interest so far! When I initially added rsyslog-mongodb I did some testing and based on that wrote README.Debian. I do not actively use it though, so I didn't follow the upstream changes for that module. Florian, from what I understand skimming over the bug report, the template parameter is no longer optional, and explicitly setting that makes ommongodb output data to the mongodb server again? If that is an intended change in behaviour or simply a bug, I dunno. Rainer sent a private reply to me after this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740869 stating that the template issue was fixed about four weeks ago. I'm not sure if that means it is fixed in a release or just in upstream Git. I think what he means is that the issue was a bug (the template parameter should not normally be mandatory) If the former, we certainly would have to update README.Debian and it also warrants a NEWS.Debian. It should be possible in that case to come up with a template which outputs the data in the format as before. If it's simply a bug, that ommongodb no longer applies a default template, then we should fix that, of course. As said, I don't actively use the plugin, so any help regarding this is very much appreciated. Hopefully the LogAnalyzer package (which will have a working config.php sample for MongoDB on localhost) will entice more users to try this and give feedback about any future regressions. Michael, if Rainer confirms the fix version for the template issue, would you mind updating the packages and then just ping me to test? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
Am 05.03.2014 20:14, schrieb Daniel Pocock: On 05/03/14 19:58, Michael Biebl wrote: Michael, if Rainer confirms the fix version for the template issue, would you mind updating the packages and then just ping me to test? Sure, no problem. I'm currently waiting for liblogging to pass the NEW queue so I can upload rsyslog 7.6.0. I expect in that case the fix will land in 7.6.1 and I would then just update to that version. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
