You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2022/02/23 18:50:28 UTC

[Bug 65914] New: Websites stop responding after update to httpd 2.4.52

https://bz.apache.org/bugzilla/show_bug.cgi?id=65914

            Bug ID: 65914
           Summary: Websites stop responding after update to httpd 2.4.52
           Product: Apache httpd-2
           Version: 2.4.52
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: All
          Assignee: bugs@httpd.apache.org
          Reporter: dwcole@oasispeo.com
  Target Milestone: ---

We had an issue  where some of  the proxy server were not  receiving any
traffic.  The access logs for the site simply flatline without errors or
entries in the httpd logs or other service level logging. Users requests would
not complete back to their browsers with no sign of any issue in the hosting
server.

This occurred  on a few difference servers that range from low  traffic and 
heavy traffic.  

The issues had occurred on the servers more than once in a day.  But on other
servers did not repeat for 3 to 4 days with no visible pattern. S

ome of the s servers were the issues occurred are used for reverse proxies, and
some are basic hosting instances.  

When the httpd  service was restarted the issue would clear up.

We had set-up to try to “freshen” server with an automated restart very early
morning and the issue still occurred without pattern or apparent reason.

We made the decision based on our analysis to revert the httpd update back to
the previous version.  We confirmed that there no SELinux conflicts.  We also
attempted to add a nightly scheduled restart and the issue would still occur.

The issue occurred on the following software version:
The OS version is 5.16.2-1.el7.elrepo.x86_64 
The httpd version is  httpd 5.4.52  (reverting to 5.4.51 stop occurrence of the
issue)

We are also using mpm in our configuration.

No related log error entries were found in any of the following log files:
/var/log/messages
/var/log/secure
/var/log/audit/audit.log
/var/log/httpd/access_log
/var/log/httpd/error_log
/var/log/httpd/(site specific}_access_log
/var/log/httpd/(site specific}_error_log
/var/log/httpd/modsec_audit

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 65914] Websites stop responding after update to httpd 2.4.52

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65914

NathanFoley <nf...@tucasi.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from NathanFoley <nf...@tucasi.com> ---
(In reply to dwcole from comment #0)
> We had an issue  where some of  the proxy server were not  receiving any
> traffic.  The access logs for the site simply flatline without errors or
> entries in the httpd logs or other service level logging. Users requests
> would not complete back to their browsers with no sign of any issue in the
> hosting server.
> 
> This occurred  on a few difference servers that range from low  traffic and 
> heavy traffic.  
> 
> The issues had occurred on the servers more than once in a day.  But on
> other servers did not repeat for 3 to 4 days with no visible pattern. S
> 
> ome of the s servers were the issues occurred are used for reverse proxies,
> and some are basic hosting instances.  
> 
> When the httpd  service was restarted the issue would clear up.
> 
> We had set-up to try to “freshen” server with an automated restart very
> early morning and the issue still occurred without pattern or apparent
> reason.
> 
> We made the decision based on our analysis to revert the httpd update back
> to the previous version.  We confirmed that there no SELinux conflicts.  We
> also attempted to add a nightly scheduled restart and the issue would still
> occur.
> 
> The issue occurred on the following software version:
> The OS version is 5.16.2-1.el7.elrepo.x86_64 
> The httpd version is  httpd 5.4.52  (reverting to 5.4.51 stop occurrence of
> the issue)
> 
> We are also using mpm in our configuration.
> 
> No related log error entries were found in any of the following log files:
> /var/log/messages
> /var/log/secure
> /var/log/audit/audit.log
> /var/log/httpd/access_log
> /var/log/httpd/error_log
> /var/log/httpd/(site specific}_access_log
> /var/log/httpd/(site specific}_error_log
> /var/log/httpd/modsec_audit


This was reported a few weeks back, just stumbled across it looking for
something else.  Hopefully you have resolved, but if not:

We had similar issues in production last week, when using MPM Event.. Sounds
like you may be suffering from this:
https://bz.apache.org/bugzilla/show_bug.cgi?id=65769

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 65914] Websites stop responding after update to httpd 2.4.52

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65914

Yann Ylavic <yl...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #2 from Yann Ylavic <yl...@gmail.com> ---
Please try r1897149 (from bug 65769) and see if it helps.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org