Update 000000_How to collect HPC Pack logs.md

kb/000000_How to collect HPC Pack logs.md

@@ -10,14 +10,14 @@
 
 ### 0. How to check HPC Pack version
 
-    Open Hpc Cluster Manager GUI -> Help -> About.
+  Open Hpc Cluster Manager GUI -> Help -> About.
 
-    Or, go to %CCP_HOME%Bin folder and check the file version of the HPC bits e.g. HpcSchedulerCore.dll.
+  Or, go to %CCP_HOME%Bin folder and check the file version of the HPC bits e.g. HpcSchedulerCore.dll.
 
 ### 1. Bin file locations
 
-    All service logs are under %CCP_DATA%LogFiles folder on the cluster nodes. The log configurations are in the service app.config file under %CCP_HOME%Bin folder.
-    > Note: the log file with the largest suffix number [N] is always empty. The latest logs are in [N-1].bin file.
+  All service logs are under %CCP_DATA%LogFiles folder on the cluster nodes. The log configurations are in the service app.config file under %CCP_HOME%Bin folder.
+  > Note: the log file with the largest suffix number [N] is always empty. The latest logs are in [N-1].bin file.
 
 * Scheduler\HpcScheduler_*.bin -- HpcScheduler service logs
 * Scheduler\HpcNodeManager_*.bin -- HpcNodeManager service logs
@@ -35,7 +35,7 @@
 * SOA\HpcSession_*.bin -- HpcSession service logs
 * SOA\HpcSoaDiagMon_*.bin -- HpcSoaDiagMon service logs
 
-    All client logs are under at %CCP_LOGROOT_USR% on the client machine. In a default install this will resolve to C:\Users\<User Profile>\AppData\Local\Microsoft\Hpc\LogFiles
+  All client logs are under at %CCP_LOGROOT_USR% on the client machine. In a default install this will resolve to C:\Users\<User Profile>\AppData\Local\Microsoft\Hpc\LogFiles
 
 * ClusterManager\HpcClusterManager_*.bin -- HpcClusterManager GUI logs
 * ClusterManager\ClusterRemoteConsole_*.bin
@@ -46,27 +46,27 @@
 
 ### 2. How to open and search logs
 
-    Use the following GUI tools
+  Use the following GUI tools
 
-    1. LogFlow – LogFlow is a graphical tool that can parse HPC logs in BIN format. It can be downloaded and installed from http://logflow.blob.core.windows.net/install/publish.htm
-    2. LogViewerUI – LogViewerUI is an alternative graphical tool that can parse HPC Pack 2016 logs. It is available here: https://hpconlineservice.blob.core.windows.net/logviewer/LogViewer.UI.application
+  1. LogFlow – LogFlow is a graphical tool that can parse HPC logs in BIN format. It can be downloaded and installed from http://logflow.blob.core.windows.net/install/publish.htm
+  2. LogViewerUI – LogViewerUI is an alternative graphical tool that can parse HPC Pack 2016 logs. It is available here: https://hpconlineservice.blob.core.windows.net/logviewer/LogViewer.UI.application
 
 ### 3. How to collect logs for Job scheduling issue
 
-    Normally we need the HpcScheduler service logs on the head node and the HpcNodeManager service logs on the compute nodes. Please indicate the job and task Ids and make sure the logs collected cover the timespan of the job and task.
+  Normally we need the HpcScheduler service logs on the head node and the HpcNodeManager service logs on the compute nodes. Please indicate the job and task Ids and make sure the logs collected cover the timespan of the job and task.
 
 ### 4. How to collect logs for Node management issue
 
-    Normally we need the HpcManagement, HpcSdm service logs on the head node and the HpcManagement service logs on the compute node. Please indicate the node name and make sure the logs collected cove the timespan of the node error.
+  Normally we need the HpcManagement, HpcSdm service logs on the head node and the HpcManagement service logs on the compute node. Please indicate the node name and make sure the logs collected cove the timespan of the node error.
 
 ### 5. How to collect logs for SOA jobs
 
-    Normally we need the HpcSession service logs on the head node, Hpcbroker service logs and HpcBrokerWorker process logs on the broker node, and HpcServiceHost process logs on the compute node.
+  Normally we need the HpcSession service logs on the head node, Hpcbroker service logs and HpcBrokerWorker process logs on the broker node, and HpcServiceHost process logs on the compute node.
 
-    * By default, HpcBrokerWorker_*.bin log files are not per session. To collect per session broker worker logs for each SOA session, on the broker node, set PerSessionLogging="1" for the shared listener “SoaListener” in HpcBrokerWorker.exe.config under %CCP_HOME%Bin on the broker nodes and then restart the HpcBroker service. After that, when a SOA session with id [SessionId] finishes, there would be a file named HpcBrokerWorker_[LogIdentifier]_[SessionId] under %CCP_DATA%LogFiles\SOA folder on the broker node. All the broker log files for this SOA session are named like HpcBrokerWorker_[LogIdentifier]_*.bin for the same LogIdentifier, they are by default 1MB files. Note if you have multiple broker nodes, you need to do the search or enable the per session logging on each broker node.
+  * By default, HpcBrokerWorker_\*.bin log files are not per session. To collect per session broker worker logs for each SOA session, on the broker node, set PerSessionLogging="1" for the shared listener “SoaListener” in HpcBrokerWorker.exe.config under %CCP_HOME%Bin on the broker nodes and then restart the HpcBroker service. After that, when a SOA session with id [SessionId] finishes, there would be a file named HpcBrokerWorker_[LogIdentifier]\_[SessionId] under %CCP_DATA%LogFiles\SOA folder on the broker node. All the broker log files for this SOA session are named like HpcBrokerWorker\_[LogIdentifier]_\*.bin for the same LogIdentifier, they are by default 1MB files. Note if you have multiple broker nodes, you need to do the search or enable the per session logging on each broker node.
 
-    * To collect HpcServiceHost logs on the compute nodes, you need to enable it in the service registration file first. Check the built-in CcpEchoSvc.config file as an example,
-    ```xml
+  * To collect HpcServiceHost logs on the compute nodes, you need to enable it in the service registration file first. Check the built-in CcpEchoSvc.config file as an example,
+  ```xml
     <system.diagnostics>
     <sources>
       <!--
@@ -105,10 +105,10 @@
       </listeners>
     </trace>
     </system.diagnostics>
-    ```
+  ```
 
-    * To colllect SOA client session api logs, please add the following in the client app.config file,
-    ```xml
+  * To colllect SOA client session api logs, please add the following in the client app.config file,
+  ```xml
     <system.diagnostics>
     <trace autoflush="true" />
     <sharedListeners>  
@@ -126,14 +126,14 @@
     </sources>
     </system.diagnostics>
 
-    ```
+  ```
 
 ### 6. How to collect logs for client side issue
 
-    Normally we may want to collect the Hpc Cluster/Job Manager or Hpc Powershell logs.
+  Normally we may want to collect the Hpc Cluster/Job Manager or Hpc Powershell logs.
 
 
 ## Status
-   1/19/2020 - Init
+  1/19/2020 - Init
 
 ## More Information