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 <markp...@gmail.com> wrote: > On Fri, May 21, 2021 at 8:49 AM jackson <jacky3...@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 >
