--_000_2A6C762D50A44D49806AFC3D2F87D8804A43412A96EX2007MBX1uzk_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello all,
I already observed in version 3.0.3 that it is impossible to acknowledge a =
problem with a service as long as the "warning" or "Critical" state is not =
"Hard". On the other hand, problems with hosts can be acknowledged while i=
n "soft" state.
Today I downloaded version 3.1.2. and this still seems to be the case.
Anybody an idea whether this is intentional or is this a bug ?
As far as I can see this can be corrected by changing one line in cgi/extin=
fo.c:
1581c1581
status=3D=3DSERVICE_WARNING || temp_svc=
status->status=3D=3DSERVICE_UNKNOWN || temp_svcstatus->status=3D=3DSERVICE_=
CRITICAL) && temp_svcstatus->state_type=3D=3DHARD_STATE){
---
> if(temp_svcstatus->status=3D=3DSERVICE_WARNING || temp_svcs=
tatus->status=3D=3DSERVICE_UNKNOWN || temp_svcstatus->status=3D=3DSERVICE_C=
RITICAL){
Sincere greetings,
--
Andr=E9 De Deurwaerder
Senior IT architect
[email protected]
+32 16 34 78 81
UZ Leuven | campus Gasthuisberg | Herestraat 49 | B - 3000 Leuven | www.uzl=
euven.be
--_000_2A6C762D50A44D49806AFC3D2F87D8804A43412A96EX2007MBX1uzk_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello all,
I already observed in version 3.0.3=
that it
is impossible to acknowledge a problem with a service as long as the
“warning” or “Critical” state is not
“Hard”. On the other hand, problems with hosts can be
acknowledged while in “soft” state.
Today I downloaded version 3.1.2. a=
nd this
still seems to be the case.
Anybody an idea whether this is int=
entional
or is this a bug ?
As far as I can see this can be cor=
rected
by changing one line in cgi/extinfo.c:
<span lang
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]