1 out of 1 rated this helpful - Rate this topic

Appendix 4: Use Tracing Log Files Generated on Windows Azure Nodes

Updated: June 7, 2012

Applies To: Windows HPC Server 2008 R2

In Windows HPC Server 2008 R2 with SP4, tracing log files are generated automatically on Windows Azure worker nodes, Windows Azure VM nodes, and Windows Azure HPC proxy nodes. The log files can help you troubleshoot issues during or after node provisioning that can cause a Windows Azure node to show a health state of Unreachable or Error, even though the Windows Azure Portal might indicate a status of Ready. The tracing log files contain the following types of information about each node:

  • Bootstrapping information for the operating system.

  • Information about the Windows HPC Server 2008 R2 services that should run on the node.

  • Information about the Hosts file.

  • Operating system performance counter data (Windows Azure worker and VM nodes only).

The log files are written to the following location on each node, as shown in the following table. The files can be manually retrieved from these locations and stored on an on-premises computer or in Windows Azure storage.

 

Windows Azure nodes Log file

Worker nodes

C:\logs\hpcworker.log

VM nodes

%CCP_HOME%Bin\hpcvm.log

HPC proxy nodes

C:\logs\hpcproxy.log

noteNote
  • Tracing log files are only maintained while the nodes remain provisioned in Windows Azure. Unless you store the files in another location, they do not persist after the Windows Azure nodes are stopped or deleted.

  • If necessary, up to five numbered overflow log files with extension .00<Integer> are written on each node.

  • Log files on each node are limited to 60 MB and then cycled automatically.

To facilitate further analysis, you can download the tracing log files from Windows Azure nodes to an on-premises computer, or upload them to a Windows Azure storage account.

To download the log files, you can use one of the following procedures:

  • Type hpcfile get at the command line to download log files from each node individually.

  • Run a script that uses hpcfile get to download files from groups of worker or VM nodes.

  • Use the Windows Azure Portal to connect remotely to each node individually. You can then copy the log file or files to a local computer.

noteNote
To download the log files from HPC proxy nodes, you must make a remote connection to each node, and then copy log files individually to a local computer.

The following are example commands and scripts that use hpcfile get to download the log files from Windows Azure worker nodes or VM nodes. For more information about command syntax, see hpcfile.

Example 1. To download the tracing log files, including possible overflow files, from the Windows Azure VM node AZURECN-001 on a cluster with a head node named myHeadNode to the current folder on the local computer, renaming the files to avoid overwriting files on the local computer:

hpcfile get /scheduler:myHeadNode /targetnode:AZURECN-001 /file:"C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\hpcvm.log" /destfile:"vm001.log"
hpcfile get /scheduler:myHeadNode /targetnode:AZURECN-001 /file:"C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\hpcvm.log.001" /destfile:"vm002.log"
hpcfile get /scheduler:myHeadNode /targetnode:AZURECN-001 /file:"C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\hpcvm.log.002" /destfile:"vm003.log"
hpcfile get /scheduler:myHeadNode /targetnode:AZURECN-001 /file:"C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\hpcvm.log.003" /destfile:"vm004.log"
hpcfile get /scheduler:myHeadNode /targetnode:AZURECN-001 /file:"C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\hpcvm.log.004" /destfile:"vm005.log"
hpcfile get /scheduler:myHeadNode /targetnode:AZURECN-001 /file:"C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\hpcvm.log.005" /destfile:"vm006.log"

Example 2. To download the tracing log files from the Windows Azure worker nodes in node group WorkerNodes with names beginning AZURECN on a cluster with a head node named myHeadNode to the C:\myFiles\myLogs folder on the local computer:

@echo off
set "extension=.log"
set "fullfilepath=C:\myFiles\myLogs"
mkdir C:\myFiles\myLogs
FOR /F "tokens=1 delims="%%G IN ('node list /group:WorkerNodes ^| FIND "AZURECN-"') DO hpcfile get /scheduler:MyHeadNode /targetnode:%%G -file:"C:\logs\hpcworker.log" /destfile:"%fullfilepath%%%G%%%extension%"

You can use one of the following procedures to upload the tracing log files from Windows Azure worker nodes and VM nodes to a Windows Azure storage account:

  1. Download one or more log files to a local computer as described in the previous section, and then upload them to a Windows Azure storage account by typing hpcpack upload at the command line.

  2. Run a script on one or more Windows Azure nodes that uses hpcpack upload to upload the log files directly to the storage account.

    noteNote
    To run a script on a group of Windows Azure nodes, you can first upload the script from a local computer to the nodes.

The following are example scripts that use hpcpack upload to upload the log files from Windows Azure worker nodes or VM nodes to the Windows Azure storage account. For more information about the command syntax, see hpcpack.

noteNote
Because log files on worker nodes are named identically, and log files on VM nodes are named identically, you should avoid overwriting files when you upload them to the Windows Azure storage account. For example, you can rename the log files with names that include the host name of the node, as shown in the following examples.

Example 3. To upload and rename the hpcworker.log file from a Windows Azure worker node to the container MyLogs in the Windows Azure storage account named MyStorageAccount with a primary key named MyPrimaryKey

@echo off
REM Get the host name of the Windows Azure node
FOR /F "usebackq" %%i IN ('e:\approot\mpiexec.exe -c 1 hostname') DO SET filename=%%i
set "extension=.log"
set "fullpath=C:\logs"
REM Consolidate the log file name (e.g., AzureCN-001.log)
set "fullfilePath=%fullpath%%filename%%extension%"
REM echo:%fullfilePath%
REM Create a temporary file with desired name
copy C:\logs\hpcworker.log %fullfilePath%
e:\approot\hpcpack upload %fullfilePath% /account:MyStorageAccount /container:MyLogs /key:MyPrimaryKey
del %fullfilePath%

Example 4. To upload a script Uploader.bat (similar to the script in Example 3) from the head node to a container named MyContainer in Windows Azure storage account named MyStorageAccount, download the script to Windows Azure nodes in the node group named WorkerNodes, and then run Uploader.bat on the nodes in WorkerNodes:

hpcpack upload uploader.bat /account:MyStorageAccount /container:MyLogs /key:MyPrimaryKey
clusrun /nodegroup:WorkerNodes hpcpack download uploader.bat /account:MyStorageAccount /container:MyLogs /key:MyPrimaryKey /path:c:\logs
clusrun /nodegroup:WorkerNodes c:\logs\uploader.bat
clusrun /nodegroup:WorkerNodes del c:\logs\uploader.bat

Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft. All rights reserved.