Summary
This article describes how to configure diagnostic tracing in FlexNet Manager Suite using *.trace files.
This style of tracing can be generated by many processes that run in the application server, beacon, and agent components. It is primarily used when the normal logging solutions do not provide enough information, even with debug settings enabled.
Trace configuration file location per component
This style of diagnostic tracing is configured using a *.trace configuration file. The name and default location of the file varies for different components as per the following table.
|
Component
|
File Name
|
Windows File Location
|
Unix File Location
|
|
Full Agent
|
etcp.trace
|
C:\Program Files (x86)\ManageSoft
|
/opt/managesoft
|
|
Lite Agent
|
ndtrack.trace
|
Wherever the ndtrack.exe is located (i.e. C:\Temp\)
|
/etc
|
|
Beacon
|
etdp.trace
|
C:\Program Files (x86)\Flexera Software\Inventory Beacon
|
N/A
|
|
Application server
|
etap.trace
|
C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform
|
N/A
|
How to configure tracing
- Take a backup copy of the configuration .trace file for the component you wish to trace.
- Open the relevant .trace file in a text editor.
- Find the "filename=..." line and specify a valid full path to a file to hold generated tracing. Create the specified directory if it does not already exist exist.
- Unless massive amounts of tracing are being generated and you don't need to know the latest tracing that has been output at any point in time, it is generally recommended to change the "flush_freq=16" setting to "flush_freq=0" in order for tracing output to be flushed to the disk after every line of output.
- Remove the "#" (comment character) from the start of appropriate trace class lines in the .trace file to specify what classes of tracing information should be generated. Usually a Flexera technical support team member will inform you of what classes to enable here. For example, uncomment the line "+Inventory" to generate tracing related to inventory gathering or processing.
- Save the updates to the .trace file.
- If you are seeking to generate tracing from a long-running process, you may need to stop and restart the relevant process to pick up changes in the .trace file. As an example, if you are tracing beacon processes you may need to restart the Flexera Beacon Engine Windows service.
- Perform the problematic action again to cause tracing to be generated.
- Inspect the generated tracing details in the file specified by the "filename=" setting.
- Once done, revert the configuration changes that were made to the .trace file to avoid generating further tracing output.
Note: Generated trace files can grow quickly, and be very large. Consider compressing trace files before sending them on to anybody else.
Related articles and resources
