Manager Log List
Log Description
Log path: The default storage path of Manager log files is /var/log/Bigdata/Manager component.
- ControllerService: /var/log/Bigdata/controller/ (OMS installation and run logs)
- HTTPd: /var/log/Bigdata/httpd (HTTPd installation and run logs)
- Logman: /var/log/Bigdata/logman (log packaging tool logs)
- NodeAgent: /var/log/Bigdata/nodeagent (NodeAgent installation and run logs)
- okerberos: /var/log/Bigdata/okerberos (okerberos installation and run logs)
- oldapserver: /var/log/Bigdata/oldapserver (oldapserver installation and run logs)
- MetricAgent: /var/log/Bigdata/metric_agent (MetricAgent run logs)
- OMM: /var/log/Bigdata/omm (OMM installation and run logs)
- Timestamp: /var/log/Bigdata/timestamp (NodeAgent startup time logs)
- Tomcat: /var/log/Bigdata/tomcat (Web process logs)
- Upgrade: /var/log/Bigdata/upgrade (OMS upgrade logs)
- UpdateService: /var/log/Bigdata/update-service (upgrade service logs)
- Sudo: /var/log/Bigdata/sudo (sudo script execution logs)
- OS: /var/log/message file (OS system logs)
- OS performance: /var/log/osperf (OS performance statistics logs)
- OS statistics: /var/log/osinfo/statistics (OS parameter configuration logs)
Log archive rule:
The automatic compression and archiving function is enabled for Manager logs. By default, when the size of a log file exceeds 10 MB, the log file is automatically compressed. The naming rule of a compressed log file is as follows: <Original log name>-<yyyy-mm-dd_hh-mm-ss>.[ID].log.zip A maximum of 20 latest compressed files are retained.
Log Type |
Log File Name |
Description |
---|---|---|
Controller run logs |
controller.log |
Log file that records component installation, upgrade, configuration, monitoring, alarm reporting, and routine O&M operations |
controller_client.log |
Run log file of the Representational State Transfer (REST) APIs |
|
acs.log |
ACS run log file |
|
acs_spnego.log |
spnego user logs in ACS |
|
aos.log |
AOS run log file |
|
plugin.log |
AOS plug-in logs |
|
backupplugin.log |
Run log file that records the backup and restoration operations |
|
controller_config.log |
Configuration run log file |
|
controller_nodesetup.log |
Controller loading task log file |
|
controller_root.log |
System log file of the Controller process |
|
controller_trace.log |
Log file that records the remote procedure call (RPC) communication between Controller and NodeAgent |
|
controller_monitor.log |
Monitoring log file |
|
controller_fsm.log |
State machine log file |
|
controller_alarm.log |
Controller alarm log file |
|
controller_backup.log |
Controller backup and recovery log file |
|
install.log, restore_package.log, installPack.log, distributeAdapterFiles.log, and install_os_optimization.log |
OMS installation log files |
|
oms_ctl.log |
OMS startup and stop log file |
|
preInstall_client.log |
Preprocessing log file before client installation |
|
installntp.log |
NTP installation log file |
|
modify_manager_param.log |
Manager parameter modification log file |
|
backup.log |
OMS backup script run log file |
|
supressionAlarm.log |
Alarm script run log file |
|
om.log |
OM certificate generation log file |
|
backupplugin_ctl.log |
Startup log file of the backup and restoration plug-in process |
|
getLogs.log |
Run log of the log collection script |
|
backupAuditLogs.log |
Run log of the audit log backup script |
|
certStatus.log |
Log file that records regular certificate checks |
|
distribute.log |
Certificate distribution log |
|
ficertgenetrate.log |
Certificate replacement log file, covering level-2 certificates, CAS certificates, and HTTPd certificates |
|
genPwFile.log |
Log file that records the generation of certificate password files |
|
modifyproxyconf.log |
Log file that records the modification of the HTTPd proxy configuration |
|
importTar.log |
Log file that records the process for importing certificates into the trust store. |
|
HTTPd |
install.log |
HTTPd installation log file |
access_log, error_log |
HTTPd run log file |
|
Logman |
logman.log |
Log packaging tool log file |
NodeAgent |
install.log and install_os_optimization.log |
NodeAgent installation log file |
installntp.log |
NTP installation log file |
|
start_ntp.log |
NTP startup log file |
|
ntpChecker.log |
NTP check log file |
|
ntpMonitor.log |
NTP monitoring log file |
|
heartbeat_trace.log |
Log file that records heartbeats between NodeAgent and Controller |
|
alarm.log |
Alarm log file |
|
monitor.log |
Monitoring log file |
|
nodeagent_ctl.log and start-agent.log |
NodeAgent startup log file |
|
agent.log |
NodeAgent run log file |
|
cert.log |
Certificate log file |
|
agentplugin.log |
Log file that records the Agent plug-in running status |
|
omaplugin.log |
OMA plug-in run log file |
|
diskhealth.log |
Disk health check log file |
|
supressionAlarm.log |
Alarm script run log file |
|
updateHostFile.log |
Host list update log file |
|
collectLog.log |
Run log file of the node log collection script |
|
host_metric_collect.log |
Run log file of host metric collection |
|
checkfileconfig.log |
Run log file of file permission check |
|
entropycheck.log |
Entropy check run log file |
|
timer.log |
Log file of scheduled node scheduling |
|
pluginmonitor.log |
Component monitoring plug-in log file |
|
agent_alarm_py.log |
Log file that records alarms upon insufficient NodeAgent file permission |
|
checkUserThread.log |
User thread usage alarm collection log file |
|
oKerberos |
addRealm.log and modifyKerberosRealm.log |
Realm handover log file |
checkservice_detail.log |
Okerberos health check log file |
|
genKeytab.log |
keytab generation log file |
|
KerberosAdmin_genConfigDetail.log |
Run log file of kadmin.conf generated during start of the kadmin process |
|
KerberosServer_genConfigDetail.log |
Run log file of krb5kdc.conf generated during start of the krb5kdc process |
|
oms-kadmind.log |
Run log file of the kadmin process |
|
oms_kerberos_install.log and postinstall_detail.log |
Okerberos installation log file |
|
oms-krb5kdc.log |
Run log file of the krbkdc process |
|
start_detail.log |
Okerberos startup log file |
|
realmDataConfigProcess.log |
Log file that records the rollback upon a realm handover failure |
|
stop_detail.log |
Okerberos stop log file |
|
oldapserver |
ldapserver_backup.log |
Oldapserver backup log file |
ldapserver_chk_service.log |
Oldapserver health check log file |
|
ldapserver_install.log |
Oldapserver installation log file |
|
ldapserver_start.log |
Oldapserver startup log file |
|
ldapserver_status.log |
Log file that records the status of the Oldapserver process |
|
ldapserver_stop.log |
Oldapserver stop log file |
|
ldapserver_wrap.log |
Oldapserver service management log file |
|
ldapserver_uninstall.log |
Oldapserver uninstallation log file |
|
restart_service.log |
Oldapserver restart log file |
|
ldapserver_unlockUser.log |
Log file that records information about unlocking LDAP users and managing accounts |
|
metric_agent |
gc.log |
MetricAgent JVM GC log file |
metric_agent.log |
Run log file of MetricAgent |
|
metric_agent_qps.log |
Log file that records MetricAgent Internal queue length and QPS information |
|
metric_agent_root.log |
All run log files of MetricAgent |
|
start.log |
Log file that records information about the MetricAgent startup and stop |
|
OMM |
omsconfig.log |
OMS configuration log file |
check_oms_heartbeat.log |
OMS heartbeat log file |
|
monitor.log |
OMS monitoring log file |
|
ha_monitor.log |
HA_Monitor operation log file |
|
ha.log |
HA operation log file |
|
fms.log |
Alarm log file |
|
fms_ha.log |
HA alarm monitoring log file |
|
fms_script.log |
Alarm control log file |
|
config.log |
Alarm configuration log file |
|
iam.log |
IAM log file |
|
iam_script.log |
IAM control log file |
|
iam_ha.log |
IAM HA monitoring log file |
|
config.log |
IAM configuration log file |
|
operatelog.log |
IAM operation log file |
|
heartbeatcheck_ha.log |
OMS heartbeat HA monitoring log file |
|
install_oms.log |
OMS installation log file |
|
pms_ha.log |
HA monitoring log file |
|
pms_script.log |
Monitoring control log file |
|
config.log |
Monitoring configuration log file |
|
plugin.log |
Monitoring plug-in run log file |
|
pms.log |
Monitoring log file |
|
ha.log |
HA run log file |
|
omm_gaussdba.log |
GaussDB HA monitoring log file |
|
gaussdb-<SERIAL>.log |
GaussDB run log file |
|
gs_ctl-<DATE>.log |
Archive log file of GaussDB control logs |
|
gs_ctl-current.log |
GaussDB control log file |
|
gs_guc-current.log |
GaussDB operation log file |
|
encrypt.log |
OMM encryption log file |
|
omm_agent_ctl.log |
OMA control log file |
|
oma_monitor.log |
OMA monitoring log file |
|
install_oma.log |
OMA installation log file |
|
config_oma.log |
OMA configuration log file |
|
omm_agent.log |
OMA run log file |
|
acs.log |
ACS resource log file |
|
aos.log |
AOS resource log file |
|
controller.log |
Controller resource log file |
|
floatip.log |
Floating IP address resource log file |
|
ha_ntp.log |
NTP resource log file |
|
httpd.log |
HTTPd resource log file |
|
okerberos.log |
Okerberos resource log file |
|
oldap.log |
OLdap resource log file |
|
tomcat.log |
Tomcat resource log file |
|
send_alarm.log |
Run log file of the HA alarm sending script of the management node |
|
pms_gc_<DATE>.log |
Monitoring GC log file |
|
pms_jstack.log |
Monitoring stack log file |
|
Timestamp |
restart_stamp |
NodeAgent startup time log file |
Tomcat |
cas.log and localhost_access_cas_log.log |
CAS run log file |
catalina.log, catalina.out, host-manager.log, localhost.log, and manager.log |
Tomcat run log file |
|
localhost_access_web_log.log |
Log file that records the access to REST APIs of FusionInsight Manager |
|
web.log |
Run log file of the Web process |
|
northbound_ftp_sftp.log, snmp.log |
Northbound log file |
|
perfStats.log |
Performance statistics log file |
|
redis_script.log |
Redis script run log file |
|
web_redis.log |
Run log file of Redis-ws |
|
update-service |
omm_upd_server.log |
UPDServer run log file |
omm_upd_agent.log |
UPDAgent run log file |
|
update-manager.log |
UPDManager run log file |
|
install.log |
Installation log file of the upgrade service |
|
uninstall.log |
Uninstallation log file of the upgrade service |
|
catalina.<Time>.log, catalina.out, host-manager.<Time>.log, localhost.<Time>.log, manager.<Time>.log, manager_access_log.<Time>.txt, web_service_access_log.<Time>.txt, catalina.log, gc-update-service.log.0.current, update-manager.controller, update-web-service.controller, update-web-service.log, commit_rm_distributed.log, commit_rm_upload_package.log, common_omagent_operator.log, forbid_monitor.log, initialize_package_atoms.log, initialize_unzip_pack.log, omm-upd.log, register_patch_pack.log, resume_monitor.logrollback_clear_patch.log, unregister_patch_pack.log, update-rcommupd.log, update-rcupdatemanager.log, and update-service.log |
Run log file of the upgrade service |
|
Upgrade |
upgrade.log_<Time> |
OMS upgrade log file |
rollback.log_<Time> |
OMS rollback log file |
|
sudo |
sudo.log |
Sudo script execution log file |
Log Levels
Table 2 describes the log levels provided by Manager. The log levels are FATAL, ERROR, WARN, INFO, and DEBUG in descending order. Logs whose levels are higher than or equal to the set level are printed by the program. The number of printed logs decreases as the set log level increases.
Level |
Description |
---|---|
FATAL |
Logs of this level record fatal error information about the current event processing that may result in a system crash. |
ERROR |
Logs of this level record error information about the current event processing, which indicates that system running is abnormal. |
WARN |
Logs of this level record abnormal information about the current event processing. These abnormalities will not result in system faults. |
INFO |
Logs of this level record normal running status information about the system and events. |
DEBUG |
Logs of this level record system information and debugging information. |
Log Formats
The following table lists the Manager log formats.
Log Type |
Component |
Format |
Example |
---|---|---|---|
Controller, HTTPd, Logman, NodeAgent, oKerberos, oldapserver, OMM, Tomcat, and upgrade |
Controller, HTTPd, Logman, NodeAgent, oKerberos, oldapserver, OMM, Tomcat, and upgrade |
<yyyy-MM-dd HH:mm:ss, SSS>|<Log Level>|<Name of the thread for which the log is generated>|<Log message>|<Location where the log event occurs> |
2020-06-30 00:37:09,067 INFO [pool-1-thread-1] Completed Discovering Node. com.xxx.hadoop.om.controller.tasks.nodesetup.DiscoverNodeTask.execute(DiscoverNodeTask.java:299) |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot