Nagios Support Forum

Hello!
I want to ask you about the check_mssql_health plug in. The plug in works properly in the server in any mode but this does not happen in Nagios web version. Could you help me with this please?

Error: UNKNOWN - cannot create status dir /var/tmp/check_mssql_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_mssql_health/cpu-busy_secs_busy_ip-server

What XI version, OS, and OS version are you using?

Can you show your service and command definition?

Hi!! thanks for you response

My server nagios is a "Nagios 3.5.1", the server OS is a centos 6.3.

the service and command is:

define service{
use generic-service
host_name DB
service_description SQL CPU
check_command check_mssql_health!ip-server!userdb!IpasswordDB!cpu-busy
}

define command{
command_name check_mssql_health
command_line $USER1$/check_mssql_health --server=$ARG1$ --username=$ARG2$ --password=$ARG3$ --mode=$ARG4$
}

This picture shows the plugin in server and the nagios web others mode!!!!

Can you send a screenshot of your login page? I think you are using Core, not XI.

For the moment though, let's assume you are using XI.

Can you PM me your Profile? You can download it by going to Admin > System Config > System Profile and click the Download Profile (not Show Profile) button in the top right corner. If for whatever reason you cannot download the profile, please put the output of Show Profile in the thread (that will at least get us some info).

After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

Hello
I guess your mistake is to test the command with the root user before generating it in nagios

The nagios user should not have the permissions to be able to write to the file, you can delete the directory
/var/tmp/check_mssql_health and force the immediate check to view result

What @nietonoshana said as far as the root user is correct, whether XI or Core.

If you are using core, you might want to think about upgrading. The current version is 4.2.3, but 4.2.4 should be coming out very soon.