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).
FusionSphere OpenStack Log Reference

FusionSphere OpenStack Log Reference

Run Logs

Description

Run logs record the real-time running information of processes in the system and show the running status of the processes. When the size of a run log file reaches 10 MB, the system compresses the log file and saves it as a backup file for tracing the process running information.

Level

Log Level

Description

DEBUG

Indicates logs that record the system running process, including information about operations performed on nodes and related parameters, such as the function entry, function exit, and module interworking interface messages.

INFO

Indicates logs that record the system running process and key involved steps, such as the module startup and active/standby switchover.

NOTICE

Indicates logs that record important normal information.

WARNING

Indicates logs that record exceptions and issues occurred during system running. The exceptions and issues will not lead to system failures. However, if they are not handled, risks, such as a backup failure, may occur.

ERROR

Indicates logs that record faults occurred during system running, for example, failures to connect to a server or database.

CRITICAL

Indicates logs that record critical faults. The faults cause the system running environment to be seriously damaged or the unavailability of some functions.

ALERT

Indicates logs that record fatal faults. The faults adversely affect system running and services in the system, for example database and service startup failures. If the faults are not rectified, the system may become unavailable.

EMERGENCY

Indicates logs that record fatal faults. The faults cause the system to be unavailable, for example, system breakdown.

Name

Run log files are named Component name.log.

.log is the run log file name extension.

The backup run log files are named Component name.log.[Serial number].gz.

  • Serial number indicates the serial number of a backup run log file. Backup run log files are numbered starting from 1 in ascending order.
  • .gz indicates the file name extension of the backup run log file.
Path

The directory for storing a run log file is the same as that for storing the backup of the log file. Table 22-8 lists the directories for storing run log files.

Table 22-8 Directory for storing operation log files

Log Type

Directory

Component log

/var/log/fusionsphere/operate/"Component name"/

MiniOS log

/var/log/fusionsphere/minios/"ip"/

Host OS log

/var/log/fusionsphere/uvp

Format

[Time] [Node] [Host ID] [Component name] [Program name] [Tag] [Log level] [Log type] [Process ID] [Thread name] [File name] [Row No.] [Function name] [Message]

NOTE:
  • Some fields in the log format are optional. Therefore, a log may contain only some of the fields.
  • Logs of third-party components, such as ZooKeeper or RabbitMQ, do not follow this format.
Parameters

Parameter

Description

Time

Specifies the time when a log is generated. The value is in the YYYY-MM-DD HH:mm:ss format.

Node

Specifies the host id of the node for which a log is generated.

Program name

Specifies the name of a program for which a log is generated.

Log level

Specifies the log level.

Log type

Specifies the log type, which can be the run log or operation log.

Process ID

Specifies the ID of the process for which a log is generated.

Thread name

Specifies the name of a thread in a process for which the log is generated.

File name

Specifies the name of the file for which a log is generated.

Row No.

Specifies the row for which a log is generated.

Function name

Specifies the function for which a log is generated.

Message

Specifies the content of a log.

Host ID

Specifies the ID of the host for which the log is generated.

Component name

Specifies the name of the component for which the log is generated, for example, novaControl.

Tag

Specifies the tag for a row in the log.

Example

An example run log is as follows:

2014-06-16T16:35:13+00:00 localhost cps-client ERROR [type:run] [pid:13052] [MainThread] [cps-clientControl:406 registerToMon] Register cps-client sucess!

Operation Logs

Description

Operation logs record operations performed by system users, such as the system administrator, O&M engineers, and system monitoring personnel, on a system. When the size of an operation log file reaches 10 MB, the system compresses the log file and saves it as a backup file for tracing the process running information.

Level

Log Level

Description

DEBUG

Indicates logs that record the system running process, including information about operations performed on nodes and related parameters, such as the function entry, function exit, and module interworking interface messages.

INFO

Indicates logs that record the system running process and key involved steps, such as the module startup and active/standby switchover.

NOTICE

Indicates logs that record important normal information.

WARNING

Indicates logs that record exceptions and issues occurred during system running. The exceptions and issues will not lead to system failures. However, if they are not handled, risks, such as a backup failure, may occur.

ERROR

Indicates logs that record faults occurred during system running, for example, failures to connect to a server or database.

CRITICAL

Indicates logs that record critical faults. The faults cause the system running environment to be seriously damaged or the unavailability of some functions.

ALERT

Indicates logs that record fatal faults. The faults adversely affect system running and services in the system, for example database and service startup failures. If the faults are not rectified, the system may become unavailable.

EMERGENCY

Indicates logs that record fatal faults. The faults cause the system to be unavailable, for example, system breakdown.

Name

Operation log files are named Component name.log.

.log is the operation log file name extension.

The backup operation log files are named Component name.log.[Serial number].gz.

  • Serial number specifies the serial number of a backup run log file. Backup run log files are numbered starting from 1 in ascending order.
  • .gz indicates the name extension of the backup operation log file.
Path

The directory for storing an operation log file is the same as the directory for storing the backup of the operation file. Table 22-9 lists the directories for storing operation log files.

Table 22-9 Directory for storing run log files

Log Type

Directory

Operation log

/var/log/fusionsphere/component/"Component name"/

Format

[Time] [Node] [Program name] [Log level] [Log type] [Process ID] [Thread name] [File name] [Row No.] [Function name] [Message]

NOTE:
  • Some fields are optional. Therefore, a log may contain only some of the fields.
  • Logs of third-party components, such as ZooKeeper or RabbitMQ, do not follow this format.
Parameters

Parameter

Description

Time

Specifies the time when a log is generated. The value is in the YYYY-MM-DD HH:mm:ss format.

Node

Specifies the host id of the node for which a log is generated.

Program name

Specifies the name of a program for which a log is generated.

Log level

Specifies the log level.

Log type

Specifies the log type, which can be the run log or operation log.

Process ID

Specifies the ID of the process for which a log is generated.

Thread name

Specifies the name of a thread in a process for which the log is generated.

File name

Specifies the name of the file for which a log is generated.

Row No.

Specifies the row for which a log is generated.

Function name

Specifies the function for which a log is generated.

Message

Specifies the content of a log.

Example

Two operation log examples are as follows:

  • Format 1:
    2017-03-21T16:35:13+00:00 localhost cps-client DEBUG [type:operate] [pid:28378] [MainThread] [utils.py:790 debug] [CLIENT:192.168.0.2] [OPERATE:host_list] [CMD:cps host-list] begin
  • Format 1:
    2017-03-21T14:06:06.921+08:00 localhost keystone-api INFO [type:operate] [pid:24259] [Dummy-9] [core.py:99 __call__] 172.28.0.2 - - - - [21/Mar/2017:06:06:06][21/Mar/2017:06:06:06] GET https://172.28.9.165:35357/identity-admin/v3 HTTP/1.1 200 268 - "curl/7.29.0"
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 4011

Downloads: 21

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