• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Issue check_nt: Could not parse arguments || Windows Server 2016 Host Error

kg28

New Pleskian
Hi,

I have Nagios Linux Server, I have added this Windows host to Nagios Server but I am getting below error

5dykvlb3rry51.png


Nagios Server Configuration as below:

====================================================================================

Windows.cfg File


define host {

use windows-server

host_name ec2-35-154-15-163.ap-south-1.compute.amazonaws.com

alias My Windows Server

address 35.154.15.163

}


Few Services Format as below:


define service {

use generic-service

host_name ec2-35-154-15-163.ap-south-1.compute.amazonaws.com

service_description NSClient++ Version

check_command check_nt!nagios@2020sg!CLIENTVERSION

}



define service {

use generic-service

host_name ec2-35-154-15-163.ap-south-1.compute.amazonaws.com

service_description CPU Load

check_command check_nt!nagios@2020sg!CPULOAD!20,40,60

}



====================================================================================

commands.cfg File

define command {

command_name check_nt

command_line $USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -v $ARG1$ $ARG2$

}

=================================================================================

I am using this on AWS EC2 instances. Please help me to understand the cause of problem.
 
Back
Top