neutron

Change log level at runtime

Bug #1555717 reported by Ramu Ramamurthy on 2016-03-10

This bug report is a duplicate of: Bug #1276694: Openstack services should support SIGHUP signal. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	neutron	New	Undecided	Unassigned

Bug Description

We need the ability to change the debug levels on the fly on neutron components (neutron-server, agents) to debug problems as they are happening.

Currently, changing log level requires a service restart (after changing the log level in the config file). Changing debug-level cannot require a restart.

We want the ability to change the log level as the service is running.

See original description

Tags:

Ramu Ramamurthy (ramu-ramamurthy) on 2016-03-10

summary:	- Change log level when running + Change log level at runtime
description:	updated
description:	updated

Revision history for this message

Assaf Muller (amuller) wrote on 2016-03-10:

You can send SIGHUP to Neutron processes to change logging levels. Adding the author of this functionality to the bug.

Revision history for this message

Ramu Ramamurthy (ramu-ramamurthy) wrote on 2016-03-10:

Will sending sighup to the process result in a restart ? ie, reload config, reinitialize rpc, resync state etc ? -

What we want is to not restart the process, but to change the log level from INFO to DEBUG for a period of time, and then change back to INFO after the debug session.

Revision history for this message

Ihar Hrachyshka (ihar-hrachyshka) wrote on 2016-03-10:

Workers will be gracefully restarted. No donwtime expected.

http://docs.openstack.org/developer/oslo.service/usage.html#signal-handling