Bug#543505: rsyslog: Wrong priority format for remote action
> Quick answer: I feel much better about 4.4.x right now. I will probably > release 4.4.1 today. FYI: 4.4.1 has been released: http://www.rsyslog.com/Article399.phtml Rainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543505: rsyslog: Wrong priority format for remote action
On Tue, 2009-09-01 at 23:48 +0200, Michael Biebl wrote: > Andreas Barth wrote: > Rainer asked me, to block rsyslog 4.4.0 as it apparently also had other issues > (iirc there was also a segfault during udp reception, but Rainer knows the > details), so it was not this specific bug report which alone was serious. > > Rainer, were you already able to nail down these issues and how far away is > the > 4.4.1 release? Quick answer: I feel much better about 4.4.x right now. I will probably release 4.4.1 today. In Depth: the segfault is not yet found, but it turns out that it was present in 4.2.0 as well. Also, only one person reported it so far and only on one of his (many) systems, this bug seems to be very related to the environment. I think this is especially true as 4.2.0 was in far more widespread use and as such I should have heard about the bug earlier/from more people if it would be likely to occur. So I conclude it is OK (though not optimal) to do a new release with this bug. I am still fighting with it. My next step is to try isolate a version where it was not present (I somewhat think it may even be present in v3 as well). To the rest of 4.4.x release, I made a mistake when I handled the beta. I moved the beta branch to quickly to a new release, without doing a stable in between. I thought I had sorted this problem out, but when I made the 4.3.2 beta stable, I obviously missed backporting some bug fixes that were present in the "newer betas". I think all of them have now been found and sorted out. There still is a chance that I may be wrong, but git log review plus absence of any more bug reports makes me think I am right. So, all in all, it probably is a good time to do a 4.4.1 release. Rainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543505: rsyslog: Wrong priority format for remote action
* Michael Biebl (bi...@debian.org) [090902 00:04]: > Otherwise I'd just downgrade this bug report to important again, to not block > the mysql transition and will upload 4.4.1 asap when it's released. It isn't necessary to downgrade the bug - I can always decide to ignore it during this specific transition, but I would like to do that only if you agree this is ok (other alternative is to break rsyslog-mysql first by keeping the current testing version of rsyslog, and then rebuilding the packages for the most important architectures in testing). Cheers, Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543505: rsyslog: Wrong priority format for remote action
Andreas Barth wrote: > * Michael Biebl (bi...@debian.org) [090901 20:58]: >> >> This is a rather important regression, so I'm raising the severity to >> serious, >> to ensure that 4.4.0-1 does not enter testing (as 4.4.0 seems to have a few >> more >> other issues, so it's better to block it) > > Can you upload the fix soon? rsyslog depends on libmysqlclient, and > this is one of the blockers to get the transition done (the other > alternative would be to potentially break rsyslog-mysql in testing - > not something I'd be happy with). Hi Rainer, Hi aba, Rainer asked me, to block rsyslog 4.4.0 as it apparently also had other issues (iirc there was also a segfault during udp reception, but Rainer knows the details), so it was not this specific bug report which alone was serious. Rainer, were you already able to nail down these issues and how far away is the 4.4.1 release? Otherwise I'd just downgrade this bug report to important again, to not block the mysql transition and will upload 4.4.1 asap when it's released. Cheers, 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#543505: rsyslog: Wrong priority format for remote action
* Michael Biebl (bi...@debian.org) [090901 20:58]: > Rainer Gerhards wrote: > >> On a client-server configuration, since my upgrading to the last unstable > >> version (on the client, the server is from stable), > >> i started to get warnings with logcheck like this : > >> > >> Aug 25 15:09:01 <86>>Aug 25 15:09:01 media CRON[15799]: > >> pam_unix(cron:session): session opened for user root by (uid=0) > >> > >> ^ priority level appears in the message > >> > >> > > Thanks tonio for the bug report and Rainer for the quick fix. > > This is a rather important regression, so I'm raising the severity to serious, > to ensure that 4.4.0-1 does not enter testing (as 4.4.0 seems to have a few > more > other issues, so it's better to block it) Can you upload the fix soon? rsyslog depends on libmysqlclient, and this is one of the blockers to get the transition done (the other alternative would be to potentially break rsyslog-mysql in testing - not something I'd be happy with). Cheers, Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#543505: rsyslog: Wrong priority format for remote action
Processing commands for cont...@bugs.debian.org: > severity 543505 serious Bug #543505 [rsyslog] rsyslog: Wrong priority format for remote action Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
