Troubleshooting

Even with the best intentions, scripts error or fail to complete as one would expect. Here is how you can troubleshoot a failing Action in BrazenCloud.

Notable BrazenAgent Paths

When a Job is submitted and the BrazenAgent is notified, it will check to see if it already has the Action cached (including checking for a newer version) and if it doesn't it will download it to the Actions Cache folder. It then expands the Action into the Working Directory (see below) where the Settings File and Results Folder are also created. The BrazenAgent will then initiate the command specified in the Manifest File and any stdout will be redirected into the std.out file.

Windows

Name	File Path
BrazenAgent Installation	C:\Program Files\BrazenCloud\<BrazenAgent ID>
BrazenAgent Logs	C:\Program Files\BrazenCloud\<BrazenAgent ID>\logs
Working Directory	C:\Program Files\BrazenCloud\<BrazenAgent ID>\work_tree\<Thread ID>\<Action Instance ID>
Results Cache	C:\Program Files\BrazenCloud\<BrazenAgent ID>\result_cache
Actions Cache	C:\Program Files\BrazenCloud\<BrazenAgent ID>\action_cache

Linux

Name	File Path
BrazenAgent Installation	/opt/brazencloud/agent/<BrazenAgent ID>
BrazenAgent Logs	/opt/brazencloud/agent/<BrazenAgent ID>/logs
Working Directory	/opt/brazencloud/agent/<BrazenAgent ID>/work_tree/<Thread ID>/<Action Instance ID>
Results Cache	/opt/brazencloud/agent/<BrazenAgent ID>/result_cache
Actions Cache	/opt/brazencloud/agent/<BrazenAgent ID>/action_cache

stdout

The BrazenAgent redirects all of the stdout from the Action to a file in the root of the executing Action called std.out. As a part of the Action completion, this file is collected and accesible in the Portal by clicking on the completed job:

Completed job

And then selecting the output icon:

stdout

This will display a text window with the entirety of the output from the job. This file can also be collected at the end of the script and submitted with the results.