Environment:
Applies to LDMS 2016 x64 based agents.
Requires Access To:
SSH to the agent you are troubleshooting.
What are we troubleshooting?
This can be used for troubleshooting many different tasks the agent performs.
Step by Step:
First you need to SSH into the Agent. Once in the agent you will be modifying the text file /opt/landesk/etc/landesk.conf file. It is always recommended to take a backup of this file prior to making changes.
If you add the following line to the bottom of the landesk.conf file: verbosity=255
Then when you run any single executable it will be picked up and verbosity will be added, however if that executable spawns another executable you will want to use the below line instead.
If you add the following line to the bottom of the landesk.conf: Overrideverbosity=255
Once you add this line even if an executable runs another the verbose will follow each process.
Example:
If you are working with map-fetchpolicy, if the line verbosity=255 is in the landesk.conf file then map-fetchpolicy will run with -V 255 added to it's parameters.
If you have the line Override verbosity=255 line added, then when map-fetchpolicy creates a vulscan job or sdclient job verbose will also be added.
You may also add the below lines to output the verbose information to a file directly. Please note this may not catch all sub processes.
logfile=/path/to/file
outputfile=/path/to/file
Equal to running a -l or -o to any given process
Override logfile=/path/to/file
Override config=/path/to/file
Adding these lines will add the -l and -c option to the various tasks