Ask the Community
Groups
How to determine process identifier of a Traverse component - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION</strong></p> <p>How to determine PID (process indentifier) of a Traverse component?</p> <p><strong>RESOLUTION</strong></p> <p>The PID of a particular Traverse component may be determined by reviewing the output from the 'netstat' for a unique TCP port used by the component of interest. See the table at the end for a list of TCP ports and their associated Traverse component.</p> <p>From a <strong>Windows</strong> command prompt, for example:</p> <blockquote class="blockquote"> <p>netstat -ano | grep 7692 | grep LISTEN</p> </blockquote> <p>where '7692' is a port number on which the Traverse component is listening:</p> <blockquote class="blockquote"> <p>TCP 0.0.0.0:7692 0.0.0.0:0 LISTENING 6648</p> </blockquote> <p>reveals the process ID to be '6648'.</p> <p> </p> <p>Similarly, from a <strong>Linux</strong> shell prompt the command is:</p> <blockquote class="blockquote"> <p>netstat -anp | grep 7692</p> </blockquote> <p>yielding output similar to:</p> <blockquote class="blockquote"> <p>tcp 0 0 0.0.0.0:7692 0.0.0.0:* LISTEN 23051/java</p> </blockquote> <p>to reveal a PID of '23051'.</p> <p> </p> <p>The following TCP ports may be substituted in the above commands that uniquely identify a particular Traverse component:</p> <blockquote class="blockquote"> <p>Web application: 7691 <br>Data Gathering Engine: 7692 <br>Message Handler: 7693 <br>Correlation & Summary Engine: 7696<br>BVE-JMS: 7697<br>Flow Analysis Engine: 7669</p> <p> </p> </blockquote> <p> </p> <p><strong>APPLIES TO </strong></p> <p>All versions of Traverse</p> <p><strong>REFERENCE </strong></p> <p>None</p> </article> </main>