KBEC-00225 - Using and collecting debug information with procmon

Article ID:360032829452
1 minute readKnowledge base

Description

An CloudBees CD (CloudBees Flow) agent starts processes that can have different execution behaviours then when the same process is started from the commandline. Often these can be traced to environment differences. If the environment shows the same, what additional debug techniques can be used?

Solution - use procmon

  1. Download and install procmon from Microsoft at https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx.

  2. Log in to the host using the agent account.

  3. Start procmon.

  4. Start the job using the command to verify that the problem is currently happening when running through CloudBees CD (CloudBees Flow) agent.

  5. Record the time in hh:mm:ss.

  6. From the commandline, run same command failing in the job step.

  7. Stop procmon (by clicking the "Magnifying Glass" button).

  8. In procmon, create a PML file with "all events" (use "File" -> "Save").

  9. Zip the PML file attach it to the ticket or upload to the ftp site.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.