2011R1.4 - Modified command

[srrhd]

Hi,

After upgrading to 2011R1.4 it appears that check_xi_service_nsclient has been modified and now had an extra argument allowing to pass the port used for polling the nrpe agents (nrpe or nsclient++)
So i simply force the port in the command, apply the configuration. It works for a while, then all of a sudden the command get back its default syntaxe. So i changed it again, apply the configuration and then use the write config tool, but again the command get reinitialise to its default.
Is it a wish from you guys that the command used for the wizard can't be modified and do i have to add the argument on all my checks ?

Aurelien.

[tonyyarusso]

I would think it would only set it whenever the Windows wizard is re-installed - how were you attempting to change it?

[srrhd]

In the configure section, on the right pannel i clicked on "command" and then edit the check_xi_service_nsclient command to replace $ARG5$ by the port value.

I never attempted to reinstall the wizard, but upgrading to R1.4 has modified this command as i didn't specified a port before and right after the upgrade all the service using it were saying something like "port value have to be an entire" or something like this.

[agriffin]

I'm not familiar with this part of the code base, but Tony should be back tomorrow to continue helping you with this issue.

[tonyyarusso]

Behavior confirmed, no it's not intentional, and I'll look into it tomorrow.

[jon.bilderback]

We updated to 2011R1.4 on Friday the 17th. Today, we added a new windows client, and all my windows clients have blown up with the error message "Server port must be an integer".

I think it might be another symptom from this modified command, and I'm going to have to shut off all alerts until we can find a fix for it. This, of course, is not acceptable.

Also, I'm looking at the release notes for R1.4, and I do not see anything that references this change.

When will we see a fix for this?

[tonyyarusso]

The reason the release notes don't reflect it is because it's actually a change just in the wizard, not the core code, which are maintained separately. As for a fix ETA, I'm hoping tomorrow.

[fao]

I am also getting these issues for Windows hosts w/ the lastest release

[mguthrie]

Yeah, this is a confirmed bug in the Windows Wizard in version 2011R1.4, tyarusso is working on a patched version which hopefully should be ready tomorrow.

[srrhd]

I don't know if a patch is needed, it might be useful for some people to specify the port.
Adding the port number as $ARG5$ in the concerned services fix evrything.