Bug#400122: sends unneccessary OK-summaries
Hi, On Monday 27 November 2006 08:29, Tore Anderson wrote: Oh, right. I think the new lsb-base-package also is directly installable - at least it used to be. Not anymore... (and the new /etc/init.d/munin-node also make use of those new lsb-function, though this is easily workaroundable by replacing it with the one from sarge ;) Say what?! There's no code whatsoever in the maintainer scripts that would change your configuration, and breaking it during upgrades would be a serious bug. Could you elaborate on this, please? yes, i can say that it's not munin related. somehow the depends where broken and so i did apt-get install -f with purged munin or munin-node and thats what broke my configuration. But, 1.2.5 seems to fix my 10:10-ok-summary problems - oh, no, lets wait, that cronjob is moved to 14:10 :) But if this is indeed the case, I will upgrade another installation and look again at those upgrade issues I had (while I was a bit stressed and didnt look closesly..) regards, Holger pgpmZon9aR3UE.pgp Description: PGP signature
Bug#400122: sends unneccessary OK-summaries
close 400122 1.2.5 thanks On Monday 27 November 2006 12:33, Tore Anderson wrote: It changed to 10:14, not 14:10, actually... You have to read crontabs backwards. heh. or more carefully :) I'm really doing to many things at the same time atm.. but I need to :( So it fixes the bug? If so may I just close this bug report? Yes done. I have no chance of getting a fix for it applied to Sarge anyway (only critical fixes are accepted there). Yup. To inform sarge users I used a versioned close :) regards, Holger pgpHVPl8RYE89.pgp Description: PGP signature
Bug#400122: sends unneccessary OK-summaries
* Holger Levsen Not anymore... (and the new /etc/init.d/munin-node also make use of those new lsb-function, though this is easily workaroundable by replacing it with the one from sarge ;) Ah, right, now I remember. If you're using it with the Sarge version of lsb-base you might experience problems using the stop parameter to the init script (there was an API change in lsb-base version 3.0-10). That's the reason the dependency is versioned. yes, i can say that it's not munin related. somehow the depends where broken and so i did apt-get install -f with purged munin or munin-node and thats what broke my configuration. Oh, okay. (Phew!) But, 1.2.5 seems to fix my 10:10-ok-summary problems - oh, no, lets wait, that cronjob is moved to 14:10 :) But if this is indeed the case, I will upgrade another installation and look again at those upgrade issues I had (while I was a bit stressed and didnt look closesly..) It changed to 10:14, not 14:10, actually... You have to read crontabs backwards. So it fixes the bug? If so may I just close this bug report? I have no chance of getting a fix for it applied to Sarge anyway (only critical fixes are accepted there). Regards -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400122: sends unneccessary OK-summaries
* Holger Levsen I upgraded to the etch-version, which I even rebuild under sarge. Besides having an unresolvable depends on an lsb-base version which is not in sarge (which I fixed by using the old init-script and making the depends versionless :), Oh, right. I think the new lsb-base-package also is directly installable - at least it used to be. it also broke my config files, so that at the moment my munin configuration is broken, even after I downgraded to the sarge version again. Say what?! There's no code whatsoever in the maintainer scripts that would change your configuration, and breaking it during upgrades would be a serious bug. Could you elaborate on this, please? -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400122: sends unneccessary OK-summaries
Hi, On Friday 24 November 2006 18:58, I wrote: Ok. I disabled always_send now. I still get alarms (just tested), enabled the 10:10 cronjob again and tomorrow morning we'll see if I get that OK-summary again or not :) I got it again :-( If I'll get them again, I'll upgrade to the etch version.. Doing so now, expect an update tomorrow... regards, Holger pgpvPqIZIDEQu.pgp Description: PGP signature
Bug#400122: sends unneccessary OK-summaries
Hi, On Friday 24 November 2006 09:25, Tore Anderson wrote: Can you try without always_send, and see if it behaves the same, and also try upgrading to 1.2.5 (the Etch package should work directly on Sarge) and see if that helps? I upgraded to the etch-version, which I even rebuild under sarge. Besides having an unresolvable depends on an lsb-base version which is not in sarge (which I fixed by using the old init-script and making the depends versionless :), it also broke my config files, so that at the moment my munin configuration is broken, even after I downgraded to the sarge version again. Doh! regards, Holger pgpp5acCDdOuF.pgp Description: PGP signature
Bug#400122: sends unneccessary OK-summaries
* Holger Levsen first of all, let me say, that munin is great! :-) But I have one problem: I use the smart plugin to monitor my harddiscs and every day shortly after 10:00 (AM) I get an email: [...] After sending this mail to the munin-users mailinglist, I learned that these mails are send by this entry in /etc/cron.d/munin: 10 10 * * * munin if [ -x /usr/share/munin/munin-limits ]; then /usr/share/munin/munin-limits --force --contact nagios --contact old-nagios; fi Strange. This entry is supposed only to apply to contacts called nagios or old-nagios, why it would cause a message to be sent for your me-contact I don't really know. I've got a email contact almost the same as your in my munin.conf, and I don't get any such mails at ten o'clock. The differences is that I don't use the always_send directive, and I'm running version 1.2.5. Can you try without always_send, and see if it behaves the same, and also try upgrading to 1.2.5 (the Etch package should work directly on Sarge) and see if that helps? -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400122: sends unneccessary OK-summaries
Hi, On Friday 24 November 2006 09:25, Tore Anderson wrote: Strange. This entry is supposed only to apply to contacts called nagios or old-nagios, why it would cause a message to be sent for your me-contact I don't really know. Heh. Guess I found a bug then :) I've got a email contact almost the same as your in my munin.conf, and I don't get any such mails at ten o'clock. The differences is that I don't use the always_send directive, and I'm running version 1.2.5. Ok. I disabled always_send now. I still get alarms (just tested), enabled the 10:10 cronjob again and tomorrow morning we'll see if I get that OK-summary again or not :) If I'll get them again, I'll upgrade to the etch version.. regards, Holger pgpyGI17AtuPG.pgp Description: PGP signature
Bug#400122: sends unneccessary OK-summaries
package: munin
version: 1.2.3-1
Hi,
first of all, let me say, that munin is great!
But I have one problem: I use the smart plugin to monitor my harddiscs and
every day shortly after 10:00 (AM) I get an email:
$domain :: $host :: S.M.A.R.T values for drive hda
OKs: Spin_Retry_Count is 100.00, Seek_Time_Performance is 100.00,
Raw_Read_Error_Rate is 100.00, Seek_Error_Rate is 100.00,
Reallocated_Sector_Ct is 100.00, Spin_Up_Time is 98.00,
Power_Off_Retract_Count is 100.00, Throughput_Performance is 100.00,
Load_Cycle_Count is 100.00.
This is because smart does a selftest.
I have the following settings in smart.conf:
contacts me
contact.me.command mail -s Munin notification ${var:host} [EMAIL PROTECTED]
contact.me.always_send warning critical
in plugin-conf.d/munin-node:
[smart_*]
user root
group disk
And I'm running debian/sarge.
After sending this mail to the munin-users mailinglist, I learned that these
mails are send by this entry in /etc/cron.d/munin:
10 10 * * * munin if [ -x /usr/share/munin/munin-limits ];
then /usr/share/munin/munin-limits --force --contact nagios --contact
old-nagios; fi
I have now disabled these summary-mails (as I'm fine with the actual alarm
mails anyway), but this is defintly a bug: a OK-summary should not be send
without a warning alarm, which I never receive(d).
This happened on three different hosts, with similar configs, though.
regards,
Holger
pgpu6TBFSpZBG.pgp
Description: PGP signature
