Re: [Nagios-devel] BUG: servicegroup and (Return code of 127 is out
Posted: Mon May 09, 2011 9:37 am
On 05/09/2011 08:56 AM, Roberto Oppedisano wrote:
> (the configuration is created via script from a DB, so the=20
> service definitions are pretty consistent).
> If I completely remove the service-group, leaving definitions the=20
> problem goes completely away.
I'd propose to doublecheck the config-generation so as to make sure that
in its output, the servicegroups are *still* the only difference. Could
you run a "diff" between the object.cache files of the two cases and
verify that?
> at the moment the problem impacts on=20
> 500+ service checks out of 8250+ (mainly the standard check_ping but=20
> also check_snmp).
check_ping and check_snmp are special in that they rely on external
executables to do the low-down work, so they have to do extra exec()s.
(check_procs would be yet another.) You might want to replace check_ping
by check_icmp, just to see what happens ...
> The very same configuration works ok on a nagios 2.9 installation (the=20
> production one which we'd like to upgrade to 3.2.x)
There *have* been some noncompatible changes between 2.x and 3.x config
syntax, so ... (Support of backslash escapes was IIRC one of them, just
to name an example.)
Kind regards,
J. Bern
--=20
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> (the configuration is created via script from a DB, so the=20
> service definitions are pretty consistent).
> If I completely remove the service-group, leaving definitions the=20
> problem goes completely away.
I'd propose to doublecheck the config-generation so as to make sure that
in its output, the servicegroups are *still* the only difference. Could
you run a "diff" between the object.cache files of the two cases and
verify that?
> at the moment the problem impacts on=20
> 500+ service checks out of 8250+ (mainly the standard check_ping but=20
> also check_snmp).
check_ping and check_snmp are special in that they rely on external
executables to do the low-down work, so they have to do extra exec()s.
(check_procs would be yet another.) You might want to replace check_ping
by check_icmp, just to see what happens ...
> The very same configuration works ok on a nagios 2.9 installation (the=20
> production one which we'd like to upgrade to 3.2.x)
There *have* been some noncompatible changes between 2.x and 3.x config
syntax, so ... (Support of backslash escapes was IIRC one of them, just
to name an example.)
Kind regards,
J. Bern
--=20
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]