Solaris server monitoring having 3rd party SSH client

[vishal313]

Hi Experts,

We have some Solaris Server to be monitored in Nagios XI 5.6.6.
These Solaris servers are using a 3rd party SSH client and not the native SSH client on the servers and hence are giving an error "Remote command execution failed: couldn't set locale correctly".
The 3rd party SSH client in this case is : Tectia SSH Client/Server.

Could you please suggest as how can we monitor a Solaris server which is having a 3rd party SSH client/Server.


Regards
Vishal Dhote

[benjaminsmith]

Hi Vishal,

This looks to be a settings issue on the Solaris server. I'm going to reach out to one the team members whose more familiar with older Unix systems for some input.

In the meantime, take a look at the following posts for some clues:

Solaris and the dreaded "couldn't set locale correctly" message

Couldn't set locale correctly

how to set solaris locale

Best Regards,
Benjamin

[vishal313]

Hi Benjamin,

Thank you for the response.
I am going through the links which you have shared, our Solaris admin has referred to those and made similar changes but that didnt help.
Looking forward to hear from you about the inputs which you get from your team member.

Regards
Vishal Dhote

[benjaminsmith]

Hi Vishal,

There is another option here. We do have Solaris, 10.x and 11.x, builds for NCPA, you can set up an agent instead of using check_by_ssh.

See: NCPA Downloads

When you login using SSH, it will pass the Lang env variable along with the LC_* . One way to resolve this would be to disable this on the remote system or try to pass the variable when loggin in using ssh, for example:

Code: Select all

LANG="en_US.UTF-8"
ssh nrpe-one "echo $LANG"

--Benjamin

Reference:
3 Ways to Fix SSH Locale Environment Variable Error

[vishal313]

Hi Benjamin,

We dont have an option to use an agent. As per our contract, we need to add and monitor servers using check_by_ssh.


Regards
Vishal Dhote

[benjaminsmith]

Hi Vishal,

Okay, did you try the suggested shh commands or disabling the locale environment variable forwarding in ssh. Let me know and post any relevant error messages to the thread.

Thanks, Benjamin