Enabling tracing for DeployR 7.2 for Windows Troubleshooting

When troubleshooting DeployR problems, it is often necessary to collect the production.log that includes debug level information to provide more detail on the problem. By default, the production.log logs only 'error' and 'info' level messages. To enable debug level tracing for the DeployR production.log on Windows and collect useful diagnostic information, do the following:

1. Stop the Apache-Tomcat-for-DeployR-7.2 service either through the Windows Services management console or, from a command line with Administrator privileges:

   C:\> net stop Apache-Tomcat-for-DeployR-7.2

2. Edit C:\Revolution\DeployR-7.2\deployr.groovy and change the two occurrences of the word 'info' in the log4j stanza to 'debug'.
   From:

       root {
           info 'stdout', 'logfile'
       }
   
       info'com.revo.phoenix'
   

   to:

       root {
           debug 'stdout', 'logfile'
       }
   
       debug'com.revo.phoenix'
   

   Save the deployr.groovy file.
3. Restart the Apache-Tomcat-for-DeployR-7.2 service either through the Windows Services management console or, from a command line with Administrator privileges:

   C:\> net start Apache-Tomcat-for-DeployR-7.2

4. Recreate the reported DeployR problem.
5. As in step 1, stop the Apache-Tomcat-for-DeployR-7.2 service to flush all messages to the production.log file.
6. Run the support data collection tool, C:\Revolution\DeployR-7.2\diagnostic\diagnostics.bat. This tool (new in DeployR 7.2) will collect the debug production.log among other diagnostic information useful for troubleshooting and package it into C:\Revolution\DeployR-7.2\diagnostic\diagnostic.zip. Provide this diagnostic.zip file to support.
7. Edit C:\Revolution\DeployR-7.2\deployr.groovy and restore the logging level from 'debug' to 'info' to reduce production.log output. Restart the Apache-Tomcat-for-DeployR-7.2 service.