> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent/9.2/cortex-xdr-agent-for-macos/troubleshooting-resources-for-mac.md).

# Troubleshooting Resources for Mac

Refer to the following troubleshooting resources for the Cortex XDR agent for Mac.

<table data-header-hidden><thead><tr><th width="160.15020751953125"></th><th width="590.1849365234375"></th></tr></thead><tbody><tr><td>Resource</td><td>Description</td></tr><tr><td>Processes</td><td><p>Launch Daemons:</p><ul><li><code>/Applications/Cortex XDR.app/Contents/MacOS/Cortex XDR</code></li><li><code>/Library/Application Support/PaloAltoNetworks/Traps/bin/pmd</code></li><li><code>/Library/Application Support/PaloAltoNetworks/Traps/bin/authorized</code></li></ul><p>Launch Agents:</p><ul><li><code>/Library/Application Support/PaloAltoNetworks/Traps/bin/Cortex XDR Agent.app/Contents/MacOS/Cortex XDR Agent</code></li></ul><p>System Extensions:</p><ul><li><code>com.paloaltonetworks.traps.securityextension</code></li><li><code>com.paloaltonetworks.traps.networkextension</code></li></ul><p>Payload:</p><ul><li><code>/Library/Application Support/PaloAltoNetworks/Traps/download/content/cortex-xdr-payload</code></li></ul></td></tr><tr><td>Cortex XDR agent installation log</td><td>Specifies any errors encountered during the installation of agent components. Use this log file when you need to troubleshoot installation issues. On Mac OS endpoints, the system records installation events in the global install log located at <code>/var/log/install.log</code>.</td></tr><tr><td>Cortex XDR agent console log</td><td><p>Indicates information, warnings, and errors related to the agent console. The Console log is located in the following folder on the endpoint:</p><ul><li>Mac OS X 10.10 and OSX 10.11—<code>/var/log/traps/agent/</code></li><li>macOS 10.12 and later releases—View logs from the Console application in <code>/Library/Logs/PaloAltoNetworks/Cortex XDR/</code>.</li></ul></td></tr><tr><td>Cortex XDR agent service log</td><td><p>Indicates information, warnings, and errors related to Cortex XDR. The Service log is located in the following folder on the endpoint:</p><ul><li>Mac OS X 10.10 and OSX 10.11—<code>/var/log/traps/</code></li><li>macOS 10.12 and later releases—View logs from the Console application in <code>/Library/Logs/PaloAltoNetworks/Cortex XDR/</code>.</li></ul></td></tr><tr><td>Supervisor Command Line Tool (cytool)</td><td>Allows you to manage agent features and perform advanced troubleshooting on the local endpoint from a command line interface. For more information, see <a href="/cortex-xdr-agent/9.2/cortex-xdr-agent-for-macos/troubleshooting-resources-for-mac/cytool-for-mac.md">Cytool for Mac</a>.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent/9.2/cortex-xdr-agent-for-macos/troubleshooting-resources-for-mac.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.