Re: Neither success nor failure?

Does the =E2=80=9Cfor cycles=E2=80=9D option work for you?  Example, =E2=80=9C=
check server xxx for 10 cycles=E2=80=9D. The cycles is the daemon interval t=
ime.=20

Thanks,

-Ron

> On Mar 13, 2025, at 12:22=E2=80=AFAM, Steven Christensen <[email protected]> w=
rote:
>=20
> =EF=BB=BF
> Hi All, I have a use case I am not sure Monit can handle. I looked at the d=
ocument and tried keywords in this mailing list, but nothing came up.
>=20
> I have a script which checks another node for some information, and then r=
eports success or failure (via exit code).The script works fine in Monit.
>=20
> But due to some dodgy DNS service, sometimes when the script tries to get i=
nformation from the other node, the DNS lookup fails. So we don't know wheth=
er the information would have resulted in a success or failure, to report to=
 Monit.=20
>=20
> My question: Is there a way to tell Monit during that script check interva=
l that the results of the check are indeterminate, that it should maintain t=
he previous success/failure state until it the next time it is able to defin=
itively report a true or false status?
>=20
> Thanks!
>=20