Red Hat Bugzilla – Bug 752469
xpbsmon spawns defunct munge processes
Last modified: 2012-08-06 22:14:03 EDT
Description of problem:
Running xpbsmon causes out-of-control spawning of defunct munge processes, eventually reaching user process limit. In ps, I see hundreds of:
rim 20104 0.0 0.0 0 0 ? Z Nov09 0:00 \_ [munge] <defunct>
Version-Release number of selected component (if applicable):
3.0.1 (at lest, that's the version number of pbs_server, can't figure how to find a separate version number for xpbsmon)
Steps to Reproduce:
1. Start xpbsmon
Process limit is reached due to defunct munge processes
No defunct munge processes created
Munge seems to be working OK otherwise. I'm happy to supply additional diagnostics, just not too clear on what to look for.
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Actually, the bug seems to have been fixed somewhere along the way anyway, it's no longer happening in Fedora 17.