Bug 67196
Summary: | Apache upgrade should restart the server | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Nathan G. Grennan <redhat-bugzilla> |
Component: | apache | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | justdave |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-06-24 02:32:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nathan G. Grennan
2002-06-20 19:58:25 UTC
The failure to restart the server after the upgrade I'm pretty sure isn't responsible for your crash. See bug 67224 and bug 67301. However, it should still be restarted after a security update if for no other reason than to make sure the security hole gets sealed in a timely manner. If we weren't running logrotate, we'd still be running the old insecure version of Apache since it never got restarted. *** This bug has been marked as a duplicate of 67301 *** Chaos: I don't think this is a duplicate.... failure to attempt to restart the server is different than the server crashing when you attempt to restart it. Can you reopen this? Actually, the root problem was that the server crashed and it was caused by the exact problem mentioned in the other bug. Restarting the server was just my workaround with my past understanding. I do think that the web server should be restarted, but I can mention that in the other bug report. |