The first place to look in this case is the size of the apache processes. Once
the OP has got on top of this - then other issues can be investigated.
So process would be:
1) Reduce number of modules in Apache (>100 at the moment) should be
around 15-25 region;
2) Look at memory u
On 14 Jan 2021, at 04:48, Jason Long wrote:
> Server have 4 CPU cores and 6GB of RAM.
> I pasted Apache configuration. In your opinion, which parts of servers must
> be examine?
Throwing more resources at the problem is not likely to fix the problem. You
need to figure out what is going on with
You should look at adding the %D and %T format strings to your httpd
access log configuration so that you can capture the amount of time
spent in delivery of a resource.
> Date: Thursday, January 14, 2021 11:48:55 +
> From: Jason Long
>
> Server have 4 CPU cores and 6GB of RAM.
> I pasted Ap
On Thu, Jan 14, 2021 at 2:14 PM Yann Ylavic wrote:
>
> You could use a "ProxyPass ... ttl=[timeout]" on the proxy with
> [timeout] < KeepAliveTimeout on the backend (say the KeepAliveTimeout
> on the backend's vhost is 5, try ttl=3 in the proxy's ProxyPass
> directive).
> By doing this, you avoid
Hi,
On Thu, Jan 14, 2021 at 11:15 AM Bram Mertens wrote:
>
> Our setup:
> Subversion 1.10 on RHEL8 served by httpd 2.4
> Reverse proxy httpd 2.4 on RHEL8
[snip backend errors]
> Am I correct to assume that it is the client (or something between the client
> and the proxy server) that is breaki
Server have 4 CPU cores and 6GB of RAM.
I pasted Apache configuration. In your opinion, which parts of servers must be
examine?
On Wednesday, January 13, 2021, 08:30:58 PM GMT+3:30, @lbutlr
wrote:
> On 12 Jan 2021, at 01:52, Jason Long wrote:
>
> It show me:
>
> 13180 X.X.X.X
>
Hi,
Our setup:
Subversion 1.10 on RHEL8 served by httpd 2.4
Reverse proxy httpd 2.4 on RHEL8
We're seeing one or more failures/day during SVN checkout/updates.
There appear to be some variations on the error:
These are the logs on the SVN (backend) server
First type:
[dav:error] Provider encounte
