16.10 - Determining the Scope of a Daemon Search - Teradata Ecosystem Manager

Teradata Ecosystem Manager User Guide

prodname
Teradata Ecosystem Manager
vrm_release
16.10
created_date
June 2017
category
User Guide
featnum
B035-3201-067K

You can use the command "ps-ef | grep" to locate daemons.

This feature cannot report metrics for a daemon if the native OS does not permit querying process metrics, for example, due to security policies.

For Microsoft Windows, you can also find the location of a daemon using the Windows Task Manager or Services console.

Searching for Daemons with Known Paths

If you know the path to the daemon, run the ps-ef command and use the output of the ps-ef command as follows:
ps-ef Command Output Executable Name Search Pattern Search Pattern Value
/opt/sampleApp/sampleExe arg1 arg2 arg3 sampleExe FullPathToProcExec /opt/sampleApp/sampleExe

Searching for Daemons using Process Command Line Arguments

To filter a daemon using command line arguments, use the output of the ps-ef command as follows:
ps-ef Command Output Executable Name Search Pattern Search Pattern Value
/bin/sh./sample.sh message 1000 localhost sampleLog1.log sh CommandLineArg ./sample.sh message 1000 localhost sampleLog1.log
Separate multiple process command lines with a space. For Microsoft Windows, use the tilde character (~) as the delimiter.

You can also use wild card characters to search for daemons. For example, to search for all daemons where the command line arguments begin with databaseProd and the other command line arguments equals tbl, the field entries are:

ps-ef Command Output Executable Name Search Pattern Search Pattern Value

/bin/sh./mover.sh databaseProdA tbl 5000

/bin/sh./mover.sh databaseProdA tbl 7000

/bin/sh./mover.sh databaseDA1 tbl 7000

sh CommandLineArg ./mover.sh databaseProd*tbl

The results of this example are the first two daemons match the search pattern value, so they are monitored.

In another example, to search for all daemons where one of the command line arguments equals databaseProd and ends with Wario, the field entries are:

ps-ef Command Output Executable Name Search Pattern Search Pattern Value

/bin/sh./load.sh databaseProd Table1Wario 5000

/bin/sh./load.sh databaseProd Table2Wario 7000

bin/sh./load.sh databaseProd Table3Sonic 7000

sh CommandLineArg ./load.sh databaseProd*Wario

The results of this example are the first two daemons match the search pattern value, so they are monitored.

Searching for Java-Based Daemons

If a java-based daemon is initiated by a fully qualified classname, the field entries are:

ps-ef Command Output Executable Name Search Pattern Search Pattern Value
/usr/bin/java -classpath /opt/sampleApp/sampleApp.jar com.sampleCom.samplePackage.sampleJavaApp java JavaFullClassName com.sampleCom.samplePackage.sampleJavaApp

If the Java-based daemon is initiated without specifying the full class name as part of the start parameter, you can search for the daemon using command line arguments. Use the output of the ps-ef command as follows:

ps-ef Command Output Executable Name Search Pattern Search Pattern Value
/usr/bin/java - D.proc.base=var/opt/app/base - Xmx512M - Dlog4j.configuration=proc.properties - jar procApp.jar java CommandLineArg -D.proc.base=var/opt/app/base - Xmx512M - Dlog4j.configuration=proc.properties - jar procApp.jar