Some of the bugs/features are difficult to implement, so it takes some time. I don't have an ETA on the bug fix at this time, but you can regularly check issue #509 on github for updates.Bug report was created 16 days ago. We have problem with basic functionalyty in production installation.
Can I find out the approximate time to solve the problem?
You can try something like this (as a starting point):I dont know how to use powershell.
1. Create a simple PS script that would check for running processes, search for "java.exe", and check the last exit code from the search. If the exit code is 0, this means the java.exe is running, else - it's not running. The script will display is simple message.
check_java.ps1
Code: Select all
Get-WmiObject Win32_Process | findstr "java.exe" >$null 2>&1
if ($LastExitCode -eq 0) {
write-host "java.exe service is running"
exit 0
} else {
write-host "java.exe service is NOT running"
exit 2
}3. Test it from the command line on the Nagios XI server.
Example:
Code: Select all
/usr/local/nagios/libexec/check_ncpa.py -H x.x.x.x -t 'mytoken' -M 'plugins/check_java.ps1'
java.exe service is runningCode: Select all
classapth = "c:\\myWebProject\\apache-tomcat-8.5.35\\bin\\bootstrap.jar;c:\\myWebProject\\apache-tomcat-8.5.35\\bin\\tomcat-juli.jar"
Get-WmiObject Win32_Process -Filter "name = 'java.exe'" | Select-Object CommandLine | Out-String -Width 1024 | findstr "$classpath" >$null 2>&1
if ($LastExitCode -eq 0) {
write-host "java.exe service is running"
exit 0
} else {
write-host "java.exe service is NOT running"
exit 2
}