Bug 820776 - beaker-proxy becomes a zombie regularly
Summary: beaker-proxy becomes a zombie regularly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-10 23:39 UTC by Nish Aravamudan
Modified: 2012-08-29 02:38 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-29 02:38:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Nish Aravamudan 2012-05-10 23:39:03 UTC
Particularly when some command throws an exception internal to beaker, but not always only then, beaker-proxy shows up as "[defunct]" in `ps aux` and a `service beaker-proxy restart` is needed. Nothing shows up in proxy.log.

Comment 1 Dan Callaghan 2012-05-14 03:58:30 UTC
The beaker-proxy daemon is a forking XMLRPC server, it forks a new process for every request (not very efficient, and I would like to change that, but that's a separate issue). The zombie processes you are seeing are probably those request handling processes, in which case it is perfectly normal and not a bug.

If the *main* beaker-proxy process is dying then that is a bug. If that is indeed happening, you could try running beaker-proxy in the foreground (-f) and see if anything useful is printed to stderr.


Note You need to log in before you can comment on or make changes to this bug.