-
Title
Reviewing KACE agent logs during troubleshooting -
Description
While reviewing the failure of a KACE Agent task, it often becomes necessary to review agent logs. Regardless on the method of gathering the agent logs, this KB is intended to assist with the basics of agent log review.
KACE Technical Support is always available to assist with log review. Please include the exact timestamp of the test (completion time of troublesome task) with the logs when creating a technical service request for assistance.
-
Resolution
Agent Log Location
- Windows: C:\ProgramData\Quest\KACE
- Mac: /Library/Application\ Support/Quest/KACE/data
- Linux: /var/quest/kace/
Gathering Logs
- Manually access directly on the agent
- See log location above
- Gather from the WebUI of the KACE Systems Management Appliance (SMA)
- Run KACE Agent Toolkit (KAT) locally or from a script
Reviewing Logs
- When opening a log, scroll to the bottom for the most recent tasks
- An exact timestamp of the test/error can be helpful with review
- Agent logs should reflect agent time zones
- Logs that roll over continue to increase in IDs as they get older
- KAgent.log would be the newest (most recent) actions
- KAgent1.log the next most recent
- KAgent2.log the third most recent
- and so forth
Most Used Keywords
Searching these files for keywords can be helpful if an exact timestamp is unknown. Additionally, knowing the IDs of certain tasks and becoming familiar with repeated phrases would allow some flexibility while searching. Certain text editors may allow for creating a language to highlight phrases in specific colors, if you find that you have to review logs on a regular basis for task evaluation.
- Error
- Fail
- Failed
- Disconnected
- exit code
- PUT /service/inventory.php
Most Used Agent Logs
The konea.log and KAgent.log are the top two most used logs when troubleshooting agent tasks. The konea.log will show all of the communication between the agent and the SMA and the KAgent.log will show all of the details of each task run on the agent.
- C:\ProgramData\Quest\KACE\konea.log - all of the communication between the agent and the SMA
- C:\ProgramData\Quest\KACE\user\KAgent.log - all of the details of each task run on the agent
- C:\ProgramData\Quest\KACE\kuid.txt - the KUID of the device (KACE Unique ID)
- C:\ProgramData\Quest\KACE\inventory.xml - the gathered details during kinventory.exe (agent inventory)
- C:\ProgramData\Quest\KACE\InventoryData.Software - the gathered details during inventory.exe (software inventory)
- C:\ProgramData\Quest\KACE\amp.conf - agent configuration file
- C:\ProgramData\Quest\KACE\user\ampinstaler.log - the agent installer log
Examples
- When troubleshooting a disconnect or what happened during communication, you would want to review the konea.log.
- When trroubleshooting a task running on the agent (script, managed install, custom inventory rule, inventory, etc), use the KAgent.log.
When these basic logs are not quite enough to evaluate the device completely, consider using the KACE Agent Toolkit (KAT) to gather additional logs.