[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-users
Subject:    Re: subversion 1.7 - Internal server error (HTTP 500) - user account gets locked out
From:       jackson <jacky3190 () gmail ! com>
Date:       2021-05-21 18:25:54
Message-ID: CA+V3yTk3GaGM7nR4_eaLb=xc-P+vzctxoz5J_z6VvhxnuL9=6w () mail ! gmail ! com
[Download RAW message or body]

HI Mark ,

  Thank you so much , i will enable the debug mode and do the testing and
let you know once done.

Thanks & Regards,
Jackson J

On Fri, May 21, 2021 at 11:35 PM Mark Phippard <markphip@gmail.com> wrote:

> On Fri, May 21, 2021 at 8:49 AM jackson <jacky3190@gmail.com> wrote:
> >
> > Hi Team,
> >
> > We are using subversion 1.7 version and we are facing issues very often
> when the users trying to commit or checkout they are getting HTTP 500 error
> and the user is getting locked out.  The users are authenticated via LDAP.
> >
> > At first we thought it was a server resource crunch issue and we
> increased the server resources but still we are getting the same problem
> >
> >
> > We have around 100+ users accessing the repos and the CPU utilization is
> normal as checked in sar report.
> >
> > Any advice on the same.
>
> If you are getting a 500 then often there will be something logged in
> the Apache error log, it might be helpful to see what error, if any is
> logged. If the errors are predictable and reproducible then setting
> Apache to log DEBUG can also help. This logs a lot though so it is
> only useful if the errors can be reproduced easily in a short amount
> of time.
>
> On the server, Subversion is not really involved in the authentication
> process. That is all handled by Apache and in this case the LDAP
> modules. The Apache httpd version will probably be more relevant than
> the Subversion version for fixes to these problems. I can recall a few
> problems where setting LDAPTimeout to a low value like 5-10 seconds
> can fix some problems. I do not remember these resulting in 500 errors
> though, I seem they were more hung connections.
>
> Maybe if something is logged in error.log it could lead to some
> solutions. From what you have provided so far though, it sounds like
> the solutions would be in Apache httpd fixes more than it would be
> Subversion.
>
> Mark
>

[Attachment #3 (text/html)]

<div dir="ltr">HI Mark ,<div><br></div><div>   Thank you so much , i will enable the \
debug mode and do the testing and let you know once \
done.</div><div><br></div><div>Thanks &amp; Regards,</div><div>Jackson \
J</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, \
May 21, 2021 at 11:35 PM Mark Phippard &lt;<a \
href="mailto:markphip@gmail.com">markphip@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, May 21, 2021 \
at 8:49 AM jackson &lt;<a href="mailto:jacky3190@gmail.com" \
target="_blank">jacky3190@gmail.com</a>&gt; wrote:<br> &gt;<br>
&gt; Hi Team,<br>
&gt;<br>
&gt; We are using subversion 1.7 version and we are facing issues very often when the \
users trying to commit or checkout they are getting HTTP 500 error and the user is \
getting locked out.   The users are authenticated via LDAP.<br> &gt;<br>
&gt; At first we thought it was a server resource crunch issue and we increased the \
server resources but still we are getting the same problem<br> &gt;<br>
&gt;<br>
&gt; We have around 100+ users accessing the repos and the CPU utilization is normal \
as checked in sar report.<br> &gt;<br>
&gt; Any advice on the same.<br>
<br>
If you are getting a 500 then often there will be something logged in<br>
the Apache error log, it might be helpful to see what error, if any is<br>
logged. If the errors are predictable and reproducible then setting<br>
Apache to log DEBUG can also help. This logs a lot though so it is<br>
only useful if the errors can be reproduced easily in a short amount<br>
of time.<br>
<br>
On the server, Subversion is not really involved in the authentication<br>
process. That is all handled by Apache and in this case the LDAP<br>
modules. The Apache httpd version will probably be more relevant than<br>
the Subversion version for fixes to these problems. I can recall a few<br>
problems where setting LDAPTimeout to a low value like 5-10 seconds<br>
can fix some problems. I do not remember these resulting in 500 errors<br>
though, I seem they were more hung connections.<br>
<br>
Maybe if something is logged in error.log it could lead to some<br>
solutions. From what you have provided so far though, it sounds like<br>
the solutions would be in Apache httpd fixes more than it would be<br>
Subversion.<br>
<br>
Mark<br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]