To troubleshoot HSNs, access the following logs:
Log Type |
Action |
Standard log file |
- From inside the VM, switch to the root user environment.
# sudo su -
- Access the standard log file1.
# /var/log/tdc-hotstandby.log
|
HSN daemon |
- From inside the VM, switch to the root user environment.
# sudo su -
- Access the HSN daemon.
# /var/log/tdc-hsn-launch.log
|
Diagnostic logs |
- From the Azure console, go to the diagnostic storage account that starts with diag.
- Look for and access tdc_hotstandby_timestamp.log to get the log of any operation.
A separate log is created each time you scale out or scale in.
|
1Each time you run the standard log file, the system saves the latest operation to /var/log/HSN/tdc-hotstandby.log and renames the current log file to /var/log/HSN/tdc-hotstandby.log.operation_number, where operation_number indicates how many operations were performed to the file.For example: - On the first run, the system saves the latest operation to .log.
- On the second run, the system renames .log to .log.1 and saves the latest operation to a new .log file.
- On the third run, the system renames .log to .log.1, renames .log.1 to .log.2, and saves the latest operation to a new .log file.
|