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
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
* 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
* 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
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
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
* 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
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
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
9 matches
Mail list logo