Hi,
On 2020-04-27 17:07:39 +0300, Sergey B Kirpichev wrote:
> On Wed, Apr 22, 2020 at 08:48:49PM +0200, mart...@tildeslash.com wrote:
> > Hello,
> >
> > the problem is fixed:
> > https://bitbucket.org/tildeslash/monit/commits/f3bea23a52db
>
> I'm glad to hear. Please try post to the bug
tags 902204 +fixed-upstream
forwarded 902204
https://bitbucket.org/tildeslash/monit/issues/840/regression-failed-link-check-generates
thanks
tag 902204 +pending
thanks
On Wed, Apr 22, 2020 at 08:48:49PM +0200, mart...@tildeslash.com wrote:
> Hello,
>
> the problem is fixed:
> https://bitbucket.org/tildeslash/monit/commits/f3bea23a52db
I'm glad to hear. Please try post to the bug thread next time.
Will be 5.27.0 soon (May?) or I
severity 902204 normal
thanks
Lowered bug severity to reflect upstream's one.
On Sun, 7 Jul 2019 09:16:45 +0300 Sergey B Kirpichev
wrote:
> forwarded 902204
> https://bitbucket.org/tildeslash/monit/issues/490/separate-link-down-and-link-error-event
> thanks
>
> Martin, please correct me if I
forwarded 902204
https://bitbucket.org/tildeslash/monit/issues/490/separate-link-down-and-link-error-event
thanks
Martin, please correct me if I set wrong upstream issue for this bug.
On Tue, 19 Feb 2019 22:47:46 +0100 "mart...@tildeslash.com"
wrote:
>
> > On 19 Feb 2019, at 02:47, Vincent
On 2019-02-17 14:13:45 +0300, Sergey B Kirpichev wrote:
> On Sat, 22 Dec 2018 03:17:27 +0100 Vincent Lefevre wrote:
> > So, it seems to be a bug in the monit code that makes it think that
> > the link is up while it is not.
> >
> > In validate.c, I see:
> >
> > [...]
> > for
tags 902204 -moreinfo
thanks
On Sat, 22 Dec 2018 03:17:27 +0100 Vincent Lefevre wrote:
> So, it seems to be a bug in the monit code that makes it think that
> the link is up while it is not.
>
> In validate.c, I see:
>
> [...]
> for (LinkStatus_T link = s->linkstatuslist; link; link =
On 2018-12-21 17:32:30 +0300, Sergey B Kirpichev wrote:
> Does it send you alert if you
> remove "if changed link capacity then alert" line too, correct?
Yes, I still get the same messages.
> If so, I suspect that the currect monit's behaviour is correct and I suggest
> you just adding "if
On Fri, Dec 21, 2018 at 01:31:40PM +0100, Vincent Lefevre wrote:
> > > > monit is spamming me with spurious "monit alert -- Link up eth0"
> > > > messages every 2 minutes! I currently have no Ethernet cable, so
> ^
> > > > that
On 2018-12-21 11:06:00 +0300, Sergey B Kirpichev wrote:
> On Sat, 23 Jun 2018 13:31:22 +0200 Vincent Lefevre wrote:
> > On 2018-06-23 12:52:56 +0200, Vincent Lefevre wrote:
> > > With the following settings:
> > >
> > > check network eth0 with interface eth0
> > > if changed link capacity
tag 902204 +moreinfo +unstable
thanks
On Sat, 23 Jun 2018 13:31:22 +0200 Vincent Lefevre wrote:
> On 2018-06-23 12:52:56 +0200, Vincent Lefevre wrote:
> > With the following settings:
> >
> > check network eth0 with interface eth0
> > if changed link capacity then alert
> >
> > monit is
On 2018-06-23 12:52:56 +0200, Vincent Lefevre wrote:
> With the following settings:
>
> check network eth0 with interface eth0
> if changed link capacity then alert
>
> monit is spamming me with spurious "monit alert -- Link up eth0"
> messages every 2 minutes! I currently have no Ethernet
Package: monit
Version: 1:5.25.2-1
Severity: important
With the following settings:
check network eth0 with interface eth0
if changed link capacity then alert
monit is spamming me with spurious "monit alert -- Link up eth0"
messages every 2 minutes! I currently have no Ethernet cable, so
13 matches
Mail list logo
