Agents are using different process causing monitoring issue: NolioAgent vs. java_real
Article ID: 201256
Updated On:
Products
Issue/Introduction
We are seeing process monitoring alerts with Nolio Release Automation Agents because one of the expected processes (NolioAgent) now has a different name - it's running under the process name: java_real
Is this a 6.7 addition?
Why are some of agents using NolioAgent vs java_real?
What is the suggested agent monitor setup for Linux Nolio Release Automation Agents?
Environment
Release : 6.7
Component: CA Release Automation Core
Cause
Is this a 6.7 addition?
It is. Since moving to AdoptOpenJDK, we had to modify the Linux JRE to include fontconfig and its dependencies in the JRE itself so that the fontconfig package wouldn't have to be separately installed on all Linux hosts that prior to upgrading Nolio agents, NAC and NES nodes.
Why are some upgraded agents using NolioAgent vs java_real?
Most likely because they are not yet upgraded to the version that uses AdoptOpenJDK.
Resolution
Version 6.6 (and below) as well as 6.7 agents can be detected with the cmd: ps x -o pid,args | grep "^.* com\.nolio\.platform\.agent\.Deployer$"
What is the suggested agent monitor setup for Linux Nolio Release Automation Agents?
We’d suggest to use Nolio Agent’s installation directory when searching through the OS processes. For example, running ps x -o pid,args, among other things, prints this:
968 /opt/ra/NolioAgent/bin/If you know your agent installation path is /opt/ra/NolioAgent, you would know to look for ^\s*\d+ /opt/ra/NolioAgent/bin/ regex-wise. If that matches, then the process is running.
Nolio Agent is two processes - the wrapper and the JVM process. If you’re intersted in checking the JVM process itself, one way is to find a process whose command line ends with com.nolio.platform.agent., so ^.* com\.nolio\.platform\.agent\..
Feedback
