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

FusionCloud 6.3.1.1 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).
Service OM Log Reference

Service OM 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.

Run log backups are the compressed backup files generated when the size of newly generated run logs reaches 20 MB. Run log backups are used to trace the records of process running information.

Level

Level Name

Level Meaning

DEBUG

Specifies logs that record the system running process including the operation information and related parameters.

INFO

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

WARN

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

ERROR

Specifies logs that record faults occurred during the system running. For example, a failure in connecting to a server or database.

Name

Naming rules for run logs: log name.log.

.log indicates the run log file name extension.

Naming rules for run log backups: log nameYYYYMMDD-HH-mm-ss.[Serial number].log.zip.

  • YYYYMMDD-HH-mm-ss indicates the time when the run log backups are generated. The letters stand for YearMonthDate-Hour-Minute-Second respectively.
  • Serial number indicates that run log backups are numbered from 1 in ascending order.
  • .zip indicates the name extension of the run log backup files.
Path

Run logs and run log backups are stored under the same path, as shown in Table 25-3.

Table 25-3 Paths where the run logs and run log backups are stored

Log Category

Path

Arcontrol process

/var/log/goku/arcontrol/

Ardata process

/var/log/goku/ardata/

Connector process

/var/log/goku/connector/

CSM process

/var/log/goku/csm/

Fault process

/var/log/goku/fault/

IRM process

/var/log/goku/irm

Gaussdb database process

/var/log/goku/postgresql

HA process

/var/log/goku/ha

HA configurations

/shelllog/

IAM process

/var/log/goku/iam

UPORTAL process

/var/log/goku/portal

Installation logs

/var/log/goku/install

OM installation logs

/var/log/

Nginx process

/var/log/goku/nginx/

Orchestrator process

/var/log/goku/orchestrator/

UHM process

/var/log/goku/uhm/

Scripts

/var/log/goku/sh_logs/

Monitor process

/var/log/goku/monitor/

OM logs saved on FSP

/var/log/fm/

Run logs of service package on Service OM

/var/log/panda/app/

Logs of some components that Service OM relies on

/var/log/panda/runtime/

Script logs on Service OM

/var/log/panda/scriptlog/

Install and backup logs on Service OM

/var/log/panda/tools/

Process run and install logs on Service OM

/var/log/panda/manager/

Alarm process logs on Service OM

/var/log/ServiceOM/omm/oms/fms/

Report process logs for alarm on Service OM

/var/log/ServiceOM/omm/oms/fmws/

Authentication process logs on Service OM

/var/log/ServiceOM/omm/oms/secs/

Report process log for authentication on Service OM

/var/log/ServiceOM/omm/oms/secws/

Format

The run log format is as follows:

[Time] [Priority] [Thread name] [Class full name Line number] Log content

Parameters

Parameter Name

Parameter Meaning

Time

Specifies the time when a log is generated, which is in the following format: YYYY(Year)-MM(Month)-DD(Date) HH(Hour):MM(Minute):SS(Second),SSS(Millisecond).

Priority

Specifies the log level, including DEBUG, INFO, WARN, and ERROR.

Thread name

Specifies the thread name. For example: Tread-37.

Class full name Line number

Specifies the class full name and the line number of a running code.

Log content

Records the log information.

Example

A typical run log is as follows:

A connector fails to connect the components.

[2013-02-27 17:02:35,610 +0800] [ERROR] [pool-2-thread-30] [com.galaxmanager.irm.connector.common.ConnectorLoginThread 244]  
ConnectorLoginThread proxy login failed getConnector is Connector [id=1, name=null, urn=null, ip=160.148.0.171, activeIp=null,  
standbyIp=null, port=8088, userName=GMRest, authToken=null, protocol=null, type=Uhm, isAvailable=false, isLogining=true,  
language=zh_CN, domain=null, description=null]!
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23000

Downloads: 37

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