Bug 1071469 (nova_debug_dump_4.0.z)

Summary:	[RFE][nova]: Provide for a live debug dump of system state
Product:	Red Hat OpenStack	Reporter:	Russell Bryant <rbryant>
Component:	openstack-nova	Assignee:	Vladan Popovic <vpopovic>
Status:	CLOSED ERRATA	QA Contact:	Vladan Popovic <vpopovic>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.0	CC:	breeler, dallan, dmaley, ndipanov, sgordon, vpopovic, xqueralt, yeylon
Target Milestone:	z4	Keywords:	FutureFeature, MoveUpstream, OtherQA, Triaged, ZStream
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-2013.2.3-3.el6ost	Doc Type:	Enhancement
Doc Text:	Feature: Added the ability to obtain a debug dump of the system state for an OpenStack service based process. For example,upon sending SIGUSR1, trigger a dump of all native threads, green threads, live config and any other relevant info. Reason: When troubleshooting production systems it is desirable to be able to trace all data base queries, web REST calls, messaging service RPC calls, and libvirt API calls associated with invocation of a user command or background job. Result: You are now able to collect timing information and stack call paths for each item as a tool for analysing a series of requests to identify slow points / scalability issues.	Story Points:	---
Clone Of:	nova_debug_dump_5.0	Environment:
Last Closed:	2014-05-29 20:35:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	913616
Bug Blocks:	1024651

Comment 1 Nikola Dipanov 2014-04-08 10:30:58 UTC

QE team: Veryfiying this can be done as follows:

1) Send all nova processes SIGUSR1
2) Make sure each one of them creates a /var/log/nova/$SERV_NAME_gurumeditation_$(date +"%Y%m%d%H%M%S") and that the file contains details about running processes threads, configuration etc.

Comment 6 errata-xmlrpc 2014-05-29 20:35:22 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0578.html