Nagios Support Forum

Hello XI support

We have followed the Wizard (Apache Tomcat), and were able to finish all the configurations, but no luck in the end: "(No output on stdout) stderr:"

Here is a command (and we could login to JMX with these credentials)

check_xi_java_as!-s service:jmx:rmi://ignored/jndi/rmi://10.X.X.X:50500/alfresco/jmxrmi -u 'monitorRole ' -p 'SuperCraneInKCForQAECM2018' -t tomcat -C 'MemorySimpleHeap,MemoryOld,MemoryMetaspace,ProcessCPUUsage,SystemCPUUsage,ThreadCount' -w '7516192768,5368709120,314572800,75,80,225' -c '8589934592,6442450944,419430400,85,90,250'!!

Please advice what went wrong with Nagios Apache monitoring in this case?

That check command looks like it shouldn't work, based off of the check_xi_java_as command definition I have on my XI machine. Can you go to Configure -> Core Config Manager -> Commands -> Search for xi_java_as -> go to the edit page for the command, and show me the definition in Command Line?

Here's what I have in mine. But best I can tell, this would not work with the check command you posted above.

mbellerue wrote:That check command looks like it shouldn't work, based off of the check_xi_java_as command definition I have on my XI machine. Can you go to Configure -> Core Config Manager -> Commands -> Search for xi_java_as -> go to the edit page for the command, and show me the definition in Command Line?

Here's what I have in mine.

Code: Select all

JAVA_ABS_PATH -Djava.class.path=$ARG2$:$USER1$/check_jvm.jar GenericASCheck $ARG1$

But best I can tell, this would not work with the check command you posted above.

This command was produced by Nagios Wizard (we've used the Wizard)
- maybe it need fixing and does not work as advertised?

This is my check_xi_java_as: /usr/bin/java -Djava.class.path=$ARG2$:$USER1$/check_jvm.jar GenericASCheck $ARG1$

check_java does not exist in XI 5.6.8 ?


---------------------------------------------

Your command did not work at all:

(No output on stdout) stderr: execvp(JAVA_ABS_PATH, ...) failed. errno is 2: No such file or directory

We have received your support ticket and will continue to troubleshoot there.