[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Ok to restart Apache?

From: Peter Kahn <pkahn_at_connected.com>
Date: 2005-03-08 16:46:20 CET

Restarting actually isn't necessary. You can perform a graceful via the
apachectl. For all new connections, the new settings will be applied.
This allows you to avoid a restart. Please be sure of two things:

1. you are performing the action as the appropriate user
                if apache or svn_user started apache and now you are
acting
                upon as root, that could lead to permissions issues

2. you apachectl is the right one.
                If you have multiple installation of apache, then you
may perform
                the graceful upon the wrong one. This can lead to a
variety of confusing
                situations.

                I recommend performing a which apachectl
                and then double checking the version of apachectl

--
Peter Kahn
pkahn@connected.com
Connected Corporation,
A subsidiary of Iron Mountain Incorporated
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2005@ryandesign.com] 
Sent: Tuesday, March 08, 2005 7:24 AM
To: Subversion List
Subject: Ok to restart Apache?
In the thread "Re: <help>Database is Wedged for the 6th time.  
Diagnostics or Prozac, anyone?" Peter Kahn wrote on 07.03.2005 at 
17:40:
> I know that prior to going to 1.1.1 and svnserve we had one crash and
> that was due to a restart of the web server in the midst of a 
> transaction.
We haven't had any problems with Subversion in the three weeks we've 
been using it, but I wanted to make sure we're not setting ourselves up 
for problems with the way we're using it.
We serve through an Apache 2 server that's also used for many other 
things, and it happens probably at least weekly that some configuration 
needs to be changed, which then means Apache has to be restarted. This 
is done at times when people could certainly be committing to the 
repository. As long as we always do a graceful restart, it seems to me 
that it should not be possible for this to cause any problems for 
Subversion. Do I see that correctly? What Subversion problems could be 
caused by doing a normal non-graceful Apache restart? Would an ongoing 
transaction simply be aborted, or do we risk repository corruption?
We're using Subversion 1.1.2 on Gentoo Linux with a single FSFS 
repository. Client access is exclusively through Apache -- no svnserve 
or direct file:/// access (although we do have a post-commit hook which 
does various things with svn and svnlook with direct file:/// URLs).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 8 16:49:05 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.