CLI works but GUI error ...

[xpertech]

The command test ok, but gui error?!

[bolson]

Hello xpertech,

You can increase the maximum message size in the command like this:

-o, --octetlength=INTEGER
max-size of the SNMP message, usefull in case of Too Long responses.
Be carefull with network filters. Range 484 - 65535, default are
usually 1472,1452,1460 or 1440.

Let us know if this resolves your issue.

[xpertech]

We already increased the size to 10000, the command output was normal. but the GUI output displayed "octet length must be <65535 and >484" ??

[bolson]

Hello expertech,

When I read the error message and look at the command output it suggests that that the output is too short ( not >484) rather than too long. That doesn't explain why it works when you test the command but not in the gui. Can you confirm that the service check command args are identical in both places?

[xpertech]

The GUI service check command args were configured same as CLI

[ssax]

Please PM me a copy of your profile, you can download it from Admin > System Profile > Download Profile so that I can look through your logs/configs to determine the issue.

Thank you

[xpertech]

Hi SSAX,

Already PM you.

[ssax]

I'm not seeing that service in your profile, did you delete it?

[xpertech]

because it keep notifying, so we disabled it.
but anyway, what could be the problem?

[lmiltchev]

I tested the plugin in-house, and it worked for me from both, the CLI, and the GUI.

because it keep notifying, so we disabled it.
but anyway, what could be the problem?

It's possible that you initially had the octet set out of the accepted range, and the service was failing because of that. Later, when you tried to modify the service (and enter the "correct" value), the changes didn't take effect for some reason. It's hard to say after the fact, especially when the service is no longer in the profile, and we are not able to review the service config. Were you able to successfully apply configuration?

It's also possible that you had multiple nagios processes running, and the wrong check was picked up...