| Summary: | httpd left 4 dead | ||
|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | dgao |
| Component: | z_other | Assignee: | John Matthews <jmatthew> |
| Status: | CLOSED NOTABUG | QA Contact: | dgao |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | skarmark |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-15 22:12:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
dgao
2011-05-12 13:58:47 UTC
One theory is that mongo is already in a semi-bad state prior to automation starting. When automation starts, it uninstall pulp packages without shutting down all the services. This could lead to something lingering, causing mongo to fully die and not clean up properly. After the new version pulp is installed, "/etc/init.d/pulp-server restart" will punt mongo into a locked state and create a cascading effect where httpd is unable to cleanup properly, and left some zombie process in the system. No more mod_python |