NRE 8.x: How to clear Java Cache, enable Java Console and Debugging.

Debugging can be enabled on the NMC's GST service. The method used is dependent on the type if issue.
Debug levels and their primary use cases are outlined in: NetWorker: Debug information levels

Approach One: NMC is not accessible, the NMC server service is failing to start.

Linux:

1. On the NMC server , open an elevated shell.
2. Create a copy of the NMC service control script:

cp /opt/lgtonmc/etc/gst_linux.sh /opt/lgtonmc/etc/gst_linux.sh.orig

3. Open the original script with a text editor:

vi /opt/lgtonmc/etc/gst_linux.sh

4. Search for the Starting GST. Add -D9 after $gstd in the Starting GST block, example:

   echo_n "Starting GST: "
      if [ -x "$gstd" ] ; then
          "$gstd" -D9
          code=$?
          echo "done."

5. Start the NMC service using the startup script:

/opt/lgtonmc/etc/gst_linux.sh start

6. Collect and review the output.

When debugging is no longer needed, revert to the original file, or remove -D9 from the Starting GST block. Manage the service using normal systemctl or service commands. For example systemctl start gst

Windows:

1. On the NMC server, open an elevated prompt. 
2. Change directory (cd) to the NMC bin directory:

cd "C:\Program Files\EMC NetWorker\Management\GST\bin"

3. Start the service with debugging enabled:

.\gstd.exe -D9

4. Collect and review the output

Approach Two: NMC is accessible and specific actions from NMC are being investigated:

1. From the NMC's Enterprise screen, click the Setup tab.
2. Click the Setup menu and select System Options.

3. From System Options, set the Debug Level as required, typically 9.

4. No service restart is required, perform actions from NMC requiring debug.
5. Render the gstd.raw from the NMC server.

Linux: /opt/lgtonmc/logs/gstd.raw
Windows (Default): C:\Program Files\EMC NetWorker\Management\GST\logs\gstd.raw

To render .raw files, see article NetWorker: How to use nsr_render_log to render .raw log files

6. Collect the rendered gstd.raw file from the NMC server.

This approach is useful for when you want to observe the Java Console events while performing actions directly within the NMC. This can be used for persistent issues, or an issue that can be reproduced on demand. This output can also be logged to a file. 

1. On the NMC client, open a Windows File Explorer.
2. Go to the NRE install location; default: C:\Program Files\NRE\java
3. Depending on the NRE version installed, a different JRE folder may be seen. To open the Java control panel, go to ..\jre#.#.#_###\bin\ and open javacpl.exe
4. Click the Advanced tab.
5. Ensure that Enable Tracing and Enable Logging are checked.
6. Click the Show Console radio button.

7. Click Apply.
8. Click Ok to close the Java control panel.
9. To Disable the console, repeat the process but select Hide Console.

This approach is useful for when you do not need the Java logging console open but would like to capture events to a log file. This is useful for intermittent issues or issues that cannot be easily reproduced on demand.

1. On the NetWorker Management Console (NMC) server, open the gconsole.jnlp file in a text editor.

• Linux: /opt/lgtonmc/web/gconsole.jnlp
• Windows (Default): C:\Program Files\EMC NetWorker\Management\GST\web\gconsole.jnlp

2. In the application-desc section, add the following options:

<argument>-f</argument>
<argument>C:\\Program Files\\NRE\\logs\\java1.log</argument>

Example:

<application-desc main-class="COM.legato.gwt.framework.LMainWindow">
		<argument>-g</argument>
		<argument>IPADDR_REPLACE_AT_RUNTIME(fe80::d3e7:121a:e342:3332)</argument>
		<argument>-p</argument>
		<argument>gconsole</argument>
		<argument>-i</argument>
		<argument>false</argument>
		<argument>-s</argument>
		<argument>X_NO_SERVER_X</argument>
		<argument>-P</argument>
		<argument>X_NO_SERVER_PORT_X</argument>
		<argument>-t</argument>
		<argument>X_NO_TASK_X</argument>
		<argument>-h</argument>
		<argument>9000</argument>
		<argument>-n</argument>
		<argument>9001</argument>
		<argument>-b</argument>
		<argument>5432</argument>
		<argument>-A</argument>
		<argument>9090</argument>
		<argument>-d</argument>
		<argument>0</argument>
		<argument>-a</argument>
		<argument>X_NO_AUTH_X</argument>
		<argument>-m</argument>
		<argument>X_NO_ISSUER_X</argument>
		<argument>-f</argument>
		<argument>C:\\Program Files\\NRE\\logs\\java1.log</argument>
</application-desc>

3. From the hosts used to access the NMC, delete the gconsole.jnlp from the NRE temp folder. The default path is C:\Program Files\NRE\temp\gconsole.jnlp. Deleting this copy of the file forces NRE to download the new updated version from the NMC server.
4. The java1.log file is created after launching the NMC:
   

1. Enable the Java Console or Output to a File as per the above sections.
2. Open the NRE NMC Launcher.
3. Log in to the NetWorker Management Console.
4. From the Enterprise window, CTRL+SHIFT+Right-Click.
5. Click Save Debug Messages… and specify an output location.

6. In the Enterprise window, CTRL+SHIFT+Right-Click again.
7. From Set Debug Level, select the wanted debug level. Usually, 7.

8. Perform actions within NMC which require debug. Copy the output from the Java Console session and collect the Java output file that is created in step 5.
9. To disable debug, repeat the process but set Debug Off.

1. On the NMC client, open a Windows File Explorer.
2. Go to the NRE install location; default: C:\Program Files\NRE\java
3. Depending on the NRE version installed, a different JRE folder may be seen. To open the Java control panel, go to ..\jre#.#.#_###\bin\ and open javacpl.exe
4. From the General tab, click Settings.

5. From the Temporary Files and Settings window, click Delete Files. 
6. Ensure Trace and Log Files and Cache Applications and Applets is checked, click Ok.

7. Click Ok to close out the remaining windows.