No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
FusionStorage Log Reference

FusionStorage Log Reference

FSA Run Logs

Description

FusionStorage Agent (FSA) run logs record the running status of FSA processes on storage nodes. The logs are stored in fixed directories and help system administrators locate faults.

Level

Level Name

Level Meaning

DEBUG

Indicates the logs that record the system running process, including operation information and related parameters of each operation.

INFO

Indicates the logs that record the system running process and key operations during system running.

WARN

Indicates the logs that record the problems or exceptions that may occur during system running.

ERROR

Indicates the logs that record the faults occurred during system running.

Name

The log files are named in dsware_agent.log.YYYY-MM-DD_HH-MM-SS format. YYYY-MM-DD_HH-MM-SS indicates the time when a log was generated.

Path

The logs are stored in /var/log/dsware/.

Format

The log format is as follows:

[Time] [Priority] [Line number] Function name: log content

Parameters

Parameter Name

Parameter Meaning

Time

Indicates the time when a log was generated. The time is in YYYY-MM-DD HH:MM:SS format.

Priority

Includes DEBUG, INFO, WARN, and ERROR.

File name, Line number

Indicates the file name and line number of a run code.

Function name: log content

Indicates the function name and log content of a run code.

Example
[2015-10-20 04:08:22:721] [INFO]  [13290] [../src/dswareAgent.c,633] read_data_from_client:fd=33,type=0x50c,len=0,verson=1

FusionStorage Run Logs

Description

FusionStorage run logs record the running status of FusionStorage processes, such as Virtual Block System (VBS), Object-based Storage Device (OSD), and MetaData Control (MDC). The server regularly collects all real-time run logs, and compresses and encrypts them. They function as backup run logs. Backup run logs are stored in fixed directories. The FusionStorage run logs help system administrators locate faults.

FusionStorage run logs are classified into real-time and backup run logs.

  • Real-time run logs: indicate the run logs that are generated by FusionStorage processes within 15 minutes. Real-time run logs are stored in /var/log/dsware/. The run logs of different processes are named in different formats.
  • Backup run logs (complete logs): indicate the run logs regularly collected. These logs are compressed and encrypted, and uploaded to the log server.
Level

Level

Description

DEBUG

Indicates the logs that record the system running process, including operation information and related parameters of each operation.

INFO

Indicates logs that record the system working process and related key operations during the system running.

WARN

Indicates the logs that record the exceptions that may occur during system running.

ERROR

Indicates the logs that record the faults occurred during system running.

Name

The real-time run log files are named in log-TYPE-ID.YYYY-MM-DD_HH-MM-SS_UUUUUU format.

  • YYYY-MM-DD_HH_MM_SS_UUUUUU indicates the time when a log was generated.
  • TYPE indicates the FusionStorage process type, such as VBS, OSD, and MDC.
  • ID indicates the VBS ID or the Electronic Serial Number (ESN) of the hard disk that houses the OSD. The value of ID is empty when the process type is the MDC.
  • log indicates the log file prefix.
NOTE:

The name of the ZooKeeper run log file is zookeeper.log.YYYY-MM-DD_HH-MM-SS.

The backup run log files are named in log[0–3].tar.gz format.

NOTE:
  • If backup run logs fail to upload to the log server, backup run logs are stored in the local node.
  • Backup run log files are automatically compressed every 15 minutes.
  • The backup run log files include FusionStorage run logs and other logs in the /var/log directory.
Path

The real-time run log files are stored in /var/log/dsware/.

Format

[Time] [Priority] [File name and line number] Function name: log content

Parameters

Parameter

Meaning

Time

Indicates the time when a log is generated. The time is in YYYY-MM-DD HH:MM:SS format.

Priority

Includes DEBUG, INFO, WARN, and ERROR.

File name and line number

Indicates the file name and line number of a run code.

Function name

Indicates the function name of a run code.

Log content

Indicates log content.

Example
[2015-07-14 18:45:04] [INFO] [../src/core/dsw_net_conn.c,363] dsw_net_conn_server_accept:accept a connection from client, accept_conn = 0x7fd269337bc0, net_point = 11, socket_fam = 0x2, local_ip = 127.0.0.1:10901, peer_ip = 127.0.0.1:37063

FusionStorage OMM Run Logs

Description

FusionStorage operation and maintenance management (OMM) run logs record the running status of OMM child processes, such as OMA, SWMA, and UPDA processes. The server regularly collects all real-time run logs, and compresses them. They function as historical run logs. Historical run logs are stored in fixed directories. FusionStorage OMM run logs help system administrators locate faults.

OMM run logs are classified into real-time run logs and historical run logs.

  • Real-time run logs: indicate the active run logs of the OMM child processes. The root directory for storing real-time run logs is /var/log/omm/. In the root directory, the real-time run logs of each child process are stored in the folders named based on the child process name.
  • Historical run logs: indicate the run logs regularly collected. These logs are compressed.
Level

Level Name

Level Meaning

DEBUG

Indicates the logs that record the system running process, including operation information and related parameters of each operation.

INFO

Indicates the logs that record the system running process and key operations during system running.

WARN

Indicates the logs that record the exceptions that may occur during system running.

ERROR

Indicates the logs that record the faults occurred during system running.

Name

The real-time run log files are named in TYPE.log format.

  • TYPE indicates the process type, such as omm_agent, omm_agt_swm, and omm_upd_agent.
  • log indicates the file name extension of run log files.

The historical run log files are named in TYPE.YYYY-MM-DD_HH-MM-SS.[ID].log.zip format.

  • TYPE indicates the process type, such as omm_agent, omm_agt_swm, and omm_upd_agent.
  • YYYY-MM-DD_HH_MM_SS indicates the time when the historical run log file was generated.
  • ID indicates the file number. The greater the ID value is, the earlier the historical run log file is generated.
  • log indicates the file name extension of run log files.
  • zip indicates the file name extension of historical run log files.
Path

The real-time run log files are stored in /var/log/omm/TYPE/.

The historical run log files are stored in /var/log/omm/TYPE/.

TYPE indicates the process type, such as oma, swma, and upda.

Format

[Time] [Priority] [Thread name] [Class name: method name, line number] [Process name] Function name: log content

Parameters

Parameter Name

Parameter Meaning

Time

Indicates the time when a log was generated. The time is in YYYY-MM-DD HH:MM:SS,MS format.

Priority

Log levels include DEBUG, INFO, WARN, and ERROR.

Thread name

Indicates the name of the active thread, for example, main, http-bio-7777-exec-5.

Class name: method name, line number

Indicates the Java class, method, and line number of a run code.

Process name

Indicates the function name, such as SWMS and PWS, of a run code.

Function name

Indicates the function name of a run code.

Log content

Indicates log content.

Example
[2015-10-20 00:22:32,150][952289150][0][ERROR][[ASSERTION FAILURE] g_PMA_SCacheMap is NULL, return[RET_VOID]!][OMA][../src/pma_data_range.c:PMA_MoveSCacheToReport,1778][omm_agent.bin,28085,35]

FusionStorage OMM Script Run Logs

Description

Script run logs record the running status of operation and maintenance management (OMM) scripts. The logs are stored in fixed directories and help system administrators locate faults.

Script run logs are classified into process installation run logs and monitoring script run logs.

  • Process installation run logs: indicate the run logs generated during the installation of the operation & maintenance agent (OMA) and operation and maintenance management (OMS).
  • Monitoring script run logs: indicate the logs generated when the control scripts that are used to monitor child OMM processes are running. The root directory for storing monitoring script run logs is /var/log/omm/. In the root directory, each child process's monitoring script run logs are stored in a folder named based on the child process name.
Level

Level Name

Level Meaning

DEBUG and TIP

Indicates the logs that record the system running process, including operation information and related parameters of each operation.

INFO

Indicates the logs that record the system running process and key operations during system running.

WARN

Indicates the logs that record the exceptions that may occur during system running.

ERROR

Indicates the logs that record the faults occurred during system running.

Name

The process installation run log files are named in install_TYPE.log format.

  • install indicates that the log records the information about process installation.
  • TYPE indicates the process type, such as oma.
  • log indicates the file name extension of run log files.

The monitoring script run log files are named in TYPE_ctl.log format.

  • TYPE indicates the type of the process that is being monitored, such as omm_agent, omm_agt_swm, and omm_upd_agent.
  • script indicates that the log records the information about process scripts.
  • log indicates the file name extension of run log files.
Path

The process installation run log files are stored in /var/log/omm/TYPE/.

The monitoring script run log files are stored in /var/log/omm/TYPE/scriptlog/.

TYPE indicates the type of the process that is being monitored, such as oma, swma, and upda.

Format

Time Priority: File name: log content

Parameters

Parameter Name

Parameter Meaning

Time

Indicates the time when a log was generated. The time is in YYYY-MM-DD HH:MM:SS format.

Priority

Log levels include TIP, DEBUG, INFO, WARN, and ERROR.

File name

Indicates the log file name of a run code.

Log content

Indicates log content.

Example
Mon Oct 19 00:00:01 2015 INFO: (4588): OMA is Running
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 3974

Downloads: 20

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next