It is about the issue of permission with Nagios.cmd
tail -f /var/log/httpd/error_log
File location : /var/log/Nagios/rw/nagios.cmd
After giving a 777 permission to this file my scheduled downtime is working fine.
Look the screenshot below.
For all type of monitoring and open source issue , Ask your query in comment box.
Windows 8.1 and Windows 10
The product key is located inside the product packaging, on the receipt or confirmation page for a digital purchase or in a confirmation e-mail that shows you purchased Windows.
If you purchased a digital copy from Microsoft Store, you can locate your product key in your Account under Digital Content.
Windows 7
The product key is located inside the box that the Windows DVD came in, on the DVD, on the receipt or confirmation page for a digital purchase or in a confirmation e-mail that shows you purchased Windows.
If you purchased a digital copy from Microsoft Store, you can locate your product key in your Account under Digital Content.
Academic Products
Your product key is located on the receipt page when you purchase or in the Order History section of the WebStore from which you ordered the software.
Devices Pre-Installed with Windows
Before using operating system copies from this site for install, re-install or recovery on devices with pre-installed operating systems, see your device manufacturer or reseller for the customized drivers and applications specific to your machine.
Using operating systems copied from this site for install, re-install or recovery may void your support agreement with your manufacturer or reseller.
Any drivers or programs that were installed by the device manufacturer or reseller may be removed during installation.
Windows 8.1 & 10:
The product key may be embedded on the motherboard or may be on the Certificate of Authenticity sticker on the bottom of the device.
Windows 7:
For devices that came with Windows 7 pre-installed, the product key may be on the Certificate of Authenticity sticker on the bottom of the device.
For more information about Windows product keys and genuine Microsoft products, see What is a product key and How to Tell site.
This means something is wrong. To find out what is wrong you need to check the NSClient++ log file. The message means that an plugin returned an invalid exit code and there can be many reasons for this but most likely something is miss configured in NSClient++ or a script your using is not working. So the only way to diagnose this is to check the NSClient++ log.
One simple way to show the log is to run in test mode like so:
net stop nscp
nscp test
… wait for errors to be reported …
exit
net start nscp
PS> cd C:\my_path\ (enter)
PS> .\run_import_script.ps1 (enter)
If it fails, you should check “setexecutionpolicy”
Steps:
In the PowerShell window, enter set-executionpolicy unrestricted.
The system will prompt to confirm the change.
Enter the letter “Y” or press the enter key to change the execution policy setting.
PowerShell’s execution policy settings dictate what PowerShell scripts can be run on a Windows system. To run the reactivateUsers script, the execution policy needs to be changed.
What am I missing??
Or: you can run the PowerShell script from cmd.exe like this:
powershell -noexit “& “”C:\my_path\run_import_script.ps1″”” (enter)
Source: http://www.cs.miami.edu
What is the process state in Unix?
This is a small experiment to show the life cycle of a Unix process. A Unix process is created in the idle state and is then moved between ready to run, running, and possibly waiting (or sleeping) , until it exits and becomes a zombie. Once a process, usually the parent process, reaps the exit status of the zombie, then the process is destroyed.
As a process executes it changes state according to its circumstances. Unix processes have the following states:
Running: The process is either running or it is ready to run.
Waiting: The process is waiting for an event or for a resource.
Stopped: The process has been stopped, usually by receiving a signal.
Zombie: The process is dead but has not been removed from the process table.
What is a zombie?
When a program forks and the child finishes before the parent, the kernel still keeps some of its information about the child in case the parent might need it – for example, the parent may need to check the child’s exit status. To be able to get this information, the parent calls `wait ()’; In the interval between the child terminating and the parent calling `wait ()’, the child is said to be a `zombie’ (If you do `ps’, the child will have a `Z’ in its status field to indicate this.)
How can a parent and child process communicate?
A parent and child can communicate through any of the normal inter-process communication schemes (pipes, sockets, message queues, shared memory), but also have some special ways to communicate that take advantage of their relationship as a parent and child. One of the most obvious is that the parent can get the exit status of the child.
write your view on this topic in the comment box!
