Logging

VCS generates two error message logs: the engine log and the agent log. Log file names are appended by letters. Letter A indicates the first log file, B the second, C the third, and so on.

The engine log is located at /var/VRTSvcs/log/engine_A.log. The format of engine log messages is:

Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI| Message Text

• Timestamp: the date and time the message was generated.
• Mnemonic: the string ID that represents the product (for example, VCS).
• Severity: levels include CRITICAL, ERROR, WARNING, NOTICE, and INFO (most to least severe, respectively).
• UMI: a unique message ID.
• Message Text: the actual message generated by VCS.

A typical engine log resembles:

The agent log is located at /var/VRTSvcs/log/agent_A.log. The format of agent log messages resembles:

Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource Name | Entry Point | Message Text

A typical agent log resembles:

Message Catalogs

VCS includes multilingual support for message catalogs. These binary message catalogs (BMCs), are stored in the following default locations. The variable language represents a two-letter abbreviation.

The VCS command-line interface displays error/success messages in any language supported by VCS. The hamsg command displays the VCS engine logs in VCS-supported languages.

The following table shows the list of BMCs