OpenStack's Log details _openstack

OpenStack Log

recently do the project used to OpenStack, because just started to use, there are a lot of errors, and then query the log, take time to get the information of the log system down, we can see.

Log is very important for a stable system, for openstack such a large system, the log is also essential, understanding the OpenStack System log is important to ensure the stability of the OpenStack environment. For a system error, it is a good practice to view the log.

OpenStack by generating a large amount of log information to help troubleshoot problems that occur during system installation runs, next describes the related log locations for several common services.

Nova Log

The OpenStack Compute Service log is located in/var/log/nova, and the default permission owner is the Nova user. It should be noted that not all log files are included on each server, for example, Nova-compute.log is generated only at compute nodes.

1. Nova-compute.log: Log generated by virtual machine instance in startup and running
2. Nova-network.log: Logs on network status, allocation, routing, and security groups
3. Nova-manage.log: Log generated when running the Nova-manage command
4. Nova-scheduler.log: Related logs for scheduling, assigning tasks to nodes, and message queues
5. Nova-objectstore.log: Mirroring related logs
6. Nova-api.log: A message-related log of user interaction with OpenStack and openstack between components
7. Related logs for Nova-cert.log:nova-cert process
8. Nova-console.log: More information on VNC services for Nova-console
9. Nova-consoleauth.log: Verification details about the Nova-console service
10. Nova-dhcpbridge.log: Network information with Dhckbridge service first off
    

Dashboard Log

Dashboard is a Django Web application that runs on the Apache server by default, and the corresponding run logs are recorded in Apache logs, and users can view them in/var/log/apache2/.

Store Log

Object Store Swift The default log is written to Syslog, which can be viewed through/var/log/syslog in the Ubuntu system and may be located in/var/log/messages on other systems.

Block storage cinder generated logs are stored by default in the/var/log/cinder directory
-Cinder-api.log: Details about the CINDER-API service
-Cinder-scheduler.log: Details about the operation of the Cinder dispatch service
-Cinder-volume.log: Log entry associated with the Cinder volume service

Keystone Log

The log of the identity authentication Keystone Service is recorded in/var/log/keystone/keystone.log.

Glance log

The mirror service glance log is stored in the/var/log/glance directory by default
-Api.log:Glance API-related logs
-Registry.log:Glance Registry Service-related logs
Depending on the log configuration, information such as meta information updates and access records is saved.

Neutron log

The log of the Network service neutron is stored in the/var/log/neutron directory by default

-Dhcp-agent.log: Log on Dhcp-agent
-L3-agent.log: Logs related to L3 agents and their functions
-Metadata-agent.log: Related logs to the Nova Metadata service via the neutron agent
-Openvswitch-agent.log: Log entry related to Openvswitch, when the implementation of the OpenStack network, if the use of different plug-ins, there will be a corresponding log file name
-Server.log: Log associated with the Neutron API service

Change the log level

The default log level for each OpenStack service is a warning level (Warning), which is sufficient to understand the state of a running system or basic error location, but sometimes it is necessary to raise the log level to help diagnose the problem, or to reduce the log level to decrease log noise. Because the log settings for each service are similar, take the Nova service for example.

Set the log level for the Nova service

Vi/etc/nova/logging.conf

Change the log level of the listed services to debug, info, or warning

[Logger_root]
Level = WARNING
handlers = null

[Logger_nova] Level
= INFO
handlers = stderr
qualname = Nova
......

Set the log level in other OpenStack services

Other services, such as Glance and Keystone, currently have log-level stars set in their primary configuration files, such as/etc/glance/glance-api.conf. You can adjust the log level to info and debug by modifying the corresponding settings in these files:

[DEFAULT]
#set INFO Log level output
verbose = False

#set debug Log level output
debug = False

 

Thank you for reading, I hope to help you, thank you for your support for this site!