Btw: you can mark the thread as resolved yourself
Btw: you can mark the thread as resolved yourself
In case you don't use the Icinga2 Agent on your Windows Server and you want/need to use check_nt there also is a pre-definde command "nscp".
To use this command to check your service you have to attach the appropriate fields to the check command. As kevin states the Icinga Director already suggests you some of the fields the check command uses when opening the drop down menu.
To use the nscp command like before you will need to create a data field "nscp_showall" beforehand:
After this you can attach the needed fields to the "nscp" command:
The next step is creating a service template that uses the configured check command and configures settings like intervals:
This service template can now be applied as a "proper" service that checks something specific on a host (like your service).
In this apply rule you define the name of your service check, e.g "SP2010 Foundation Search Service" and apply this check to your "Sharepoint Host".
Also you have to set the needed variables in the corresponding data fields:
As this thread has been "dug up" ;):
Just in case someone is looking for a workaround for scheduled downtimes before they are configurable via Direcot:
Currently I configure scheduled downtimes as a config file on the Icinga2 master server.
following an example for a flexible downtime that startes between 00:15 und 01:30
It works and keeps your checks working 24x7, so there is no gap in perfdata for example.
Forgive me if this is completely wrong, as I am not familiar with the Icinga2 Agent for Windows (bc I still use the standalone NSClient for that).
I assume, that the check commands in director with ".exe" are the ones that are provided/used by the Icinga2 Agent?
Then why not use the service-windows (check_service.exe) command to check different services?
Could this maybe be the problem?
The documentation states, that you should define the duration in seconds (https://docs.icinga.com/icinga…actions-schedule-downtime) as duration is an interger field.
Or is the automatic conversion also working here (souldn't it be 30m then :D)?
there is also an argument for object_type:
If I see this correct, you created a service, but it is not bound to anything, so it does not show at any host.
here is how a service template and an applied service look like:
so I'd say, you need to create an apply rule that imports your service template and assign it to a host.
your check script check_apache_status.pl is not in the folder /usr/lib64/nagios/plugins or it is not readable/executable for Icinga2.
icinga2 run under user "nagios" (if ubuntu) or icinga (if centos).
Can you be more precise as to what you mean by
.is there any way to find some built in check command like the nagios plugins.
In the command list inside Icinga Director all commands displayed with a "pin" in the front are pre-defined.
The are ready to use, you only need to configure:
1. the needed fields for the arguments
2. the corresponding plugin script in /usr/lib/nagios/plugins
3. a service template that uses the check command
Thanks for the quick answer!
Will test setting the ntp server to their local DC.
The ntp check is a good idea, hadn't thought of it
Do you have the scripts that these commands need in the respective folder?
Default for "PluginDir" is "/usr/lib/nagios/plugins"
So you will need your "check_updates" script in this folder, as well as any other script you want to execute.
Concerning your command:
Why the skip_key for your "-c" argument?
to get more scripts in you PluginDir you can install these packages (example for Ubuntu):
I'm having a question(or some :D) concerning an Icinga2 setup with satellites in different time zones.
The system has a master and a satellite in time zone Europe/Berlin, one satellite in the US and one in South Korea (don't know the exact location of those two).
As of know I have set up ntp on all of these machines and configured it to "Europe/Berlin".
The reasons I did this are:
1. the customer has disabled Hyper-V time sync for the guest machines
2. before the ntp setup, checks were often overdue
The disabled Hyper-V time sync also leads to the problem, that Icinga2 starts with the "random time" the Hyper-V injects (e.g. two months in the future).
To work around this I added the ntp service to the requirements in the icinga2 system.d script.
Is setting all sattellites to the same time zone the correct way?
I have read, that IcingaWeb2 takes the time zone from the browser and converts timestamps to UTC internally. Can this and the ntp settings combined, be a problem when someone from, lets say, South Africa works with IcingaWeb2.
I'm not sure, to be honest, as I can only work on the system, when the customer lets me
Last update of Icinga2 and IcingaWeb2 I did was around March '17
If I can provied anything else, pls tell me.
Thanks and greetings
I haven't configured anything knowingly.
SELinux isn't installed,
AppArmor gives me this:
Checkresults for removed "o" permissions:
ERROR: Icinga\Exception\ConfigurationError in /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Backend/MonitoringBackend.php:181 with message: No backend has been configured
I already added the nagios user to the icingaweb2 group: icingaweb2:x:117:www-data,nagios
That's why I was so irritated that it did not work and why I even tried the o+r and o+x "way".
I found a solution:
chmod o+x -R /etc/icingaweb2/ did the trick
Isn't the pre-defined command still using the deprecated order?
I'll push this up again, as I can't find a solution
edit: I found a solution:
chmod o+x -R /etc/icingaweb2/...
Thanks Wolfang, I forgot to point that out more clearly.
I was aiming at this problem/solution: https://github.com/Icinga/icingaweb2-module-pnp/issues/18
As you install pnp4nagios from packages this shouldn't concern you, I think, as I experienced this problem only with a manual installation under ubnuntu 16.04.
You could check here (https://www.thomas-krenn.com/d…usty?xtxsearchselecthit=1), if the configuration is correct.
So if you are working with agents on your hosts than you should refer to this: https://github.com/Icinga/icin…24-Working-with-agents.md
I can't help you there, as I am not working with agents in my setup.