Extracting and collecting logs is most useful when errors occur and log files need to be viewed by GSC or Engineering for problem debugging and analysis. It can also be used to simply save a record of the upgrade for future viewing.
Log Collection
By default, the PUT master node log files are collected, but the operation also allows you to select other nodes to collect the log files from. For example, if you encountered an error on a particular node other than the PUT master node, you would want to select that node to collect log files.
Relevant log files are collected into a single zipped file in /var/opt/teradata/TDput/fileservice/Logs date.zip.
Log File Types
There are various types of log files.| Log File | Description |
|---|---|
| /var/log/messages | Contains events logged by kernel printk() and syslog(3) messages. On Redhat, this also contains the boot messages. |
|
/var/log/boot.msg /var/log/boot.log |
Contains the boot messages and kernel startup logs on SUSE. Contains the boot messages on Redhat. |
| /var/log | Other miscellaneous log files. |
Log Extraction
The Log Collection operation can also be used to extract logs by choosing the Extract option. Extract works similarly to the command line tool used to extract logs.
Emergency Log Collection
The Log Collection operation can be run in a simplified form during any operation (only after the Select Nodes step completes) using Emergency Log Collection. Collecting logs during an operation is useful in situations where exiting the currently running operation to get logs can be fatal to the system or the action being performed.
While an operation is running, you can click the Logs (HTML format) link at the bottom of the screen to open the Logs & Reports view for the operation. In the Log files on this host section, click the Emergency Log Collect link to open a screen where you can choose the nodes to collect logs from in the list of selected nodes. The master node must always be selected and is selected by default.
When the logs are collected, a results screen appears. This screen lists the nodes PUT was able to collect logs from and the location where those logs are stored. If PUT was unable to collect logs from a node, an error message is displayed.