I've tried every variation I can think of for the repository_dir setting.
Things like c:\\svn\\LTM, c://svn//ltm, ../../ltm, etc.  Each time I updated
the path, I would run a trac-admin resync to make sure that the path was
valid for trac, and each time it resync'd properly through all of the
revisions in SVN.

Unfortunately, I'm still seeing the same behavior with Apache crashing every
time.  I'm wondering now if it has something to do with the new User Access
Control (UAC) built-in to SBS 2008.  I've noticed other strange behavior
with Apache command line functions requiring me to right click and select
"Run As Administrator" when opening a command prompt.  When using htpasswd
it will run normally and give no errors if I have a normal command prompt,
but nothing will happen in my passwd file unless I have Run As Administrator
going.  Weird, since my account is an Admin account.

Later tonight when server usage is low, I'll attempt to turn off UAC and see
if that leads to any progress.  I'll ping the Apache forums tomorrow if I
don't get things working tonight.  Any other ideas are welcome - I'm willing
to try just about anything (other than switching to Linux of course).

Thanks - Dave



On Wed, Jun 3, 2009 at 5:24 PM, Lance Hendrix <[email protected]>wrote:

>
> This looks like an Apache issue (specifically with the apache apr
> library), but I might have a few ideas.  It will take me a little while
> to get to this, but I should be able to try to reproduce in the next day
> or so.  In the meantime, try different variations of the
> "repository_dir".  For instance try to use double slashes and see if
> that works "c:\\svn\\ltm" or if "c:/svn/ltm" or "/svn/ltm" etc will work
> for you...
>
> FYI, (from http://apr.apache.org/)
> "The mission of the Apache Portable Runtime (APR) project is to create
> and maintain software libraries that provide a predictable and
> consistent interface to underlying platform-specific implementations.
> The primary goal is to provide an API to which software developers may
> code and be assured of predictable if not identical behavior regardless
> of the platform on which their software is built, relieving them of the
> need to code special-case conditions to work around or take advantage of
> platform-specific deficiencies or features."
>
> Which is why I am wondering if it is not an issue with the
> "repository_dir" path, but I must admit that I have little experience
> with Trac on Windows (just a some experience with Windows and Apache/PHP
> and Windows in general)...
>
> Otherwise, it might be something that you might want to take to the
> Apache forums/lists...
>
> Let me know if you make any headway from your end.
>
> Lance
>
> David Headley wrote:
> > I just tried to run Apache as an application (with Run As
> > Administrator) instead of a service, and noticed that the app crashes
> > when I go to the trac URL.  I went back into the Event Viewer and the
> > Apache service crashes every time I try to connect to Trac:
> >
> > Faulting application httpd.exe, version 2.2.11.0, time stamp
> > 0x493f5d44, faulting module libapr.dll, version 0.9.17.0, time stamp
> > 0x4878c068, exception code 0xc0000005, fault offset 0x000139c1,
> > process id 0x15d8, application start time 0x01c9e495a599432c.
> >
> > That explains why the page load error appears and I get a
> > "interrupted" notice instead of a 401 or 404 or whatever.
> >
> > Has anyone seen this happen before?
> >
> > Thanks - David
> >
> >
> > On Wed, Jun 3, 2009 at 2:11 PM, David Headley <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     Thanks for the reply Lance.  I wondered the same thing the other
> >     day, but I just rechecked to be sure.
> >
> >     Apache is running as a service under the LOCAL SYSTEM account.
> >     The SVN directory tree allows the SYSTEM account full control.  I
> >     changed the Apache service to Log On using my username and
> >     password to be sure, but I still see the same behavior.
> >
> >     Are the authz_file and authz_module_name necessary for the initial
> >     connection of trac to SVN?  I currently have those lines unset in
> >     trac.ini, but I'm using an svnaccessfile to control user
> >     permissions on SVN.
> >
> >     From my Apache httpd.conf:
> >     ...
> >       LoadModule authz_svn_module modules/mod_authz_svn.so
> >     ...
> >     WSGIScriptAlias /trac /svn/trac/test/apache/trac.wsgi
> >     <Directory /svn/trac/test/apache>
> >         WSGIApplicationGroup %{GLOBAL}
> >         Order deny,allow
> >         Allow from all
> >     </Directory>
> >
> >     Thanks - Dave
> >
> >
> >
> >     On Wed, Jun 3, 2009 at 11:37 AM, Lance Hendrix
> >     <[email protected] <mailto:[email protected]>> wrote:
> >
> >
> >         Sounds like it might be a permissions issue with Apache and
> >         the SVN
> >         directory.  I assume you are running as (or in) the administrator
> >         (group) when you are using trac-admin, so when you do command
> line
> >         stuff, it is accessing SVN with credentials as an administrator;
> >         however, I also assume that the account that Apache is running
> >         under is
> >         not a member of the administrators group, so this "sounds" like a
> >         typical permissions problem.
> >
> >         Check the account that Apache is running under and ensure that
> the
> >         directory your SVN repository is located in has the proper
> >         permissions
> >         (and subdirectories, so your subdirectories should inherit
> >         permissions
> >         from the parent) for the account that Apache is running under.
> >
> >         This would be my first guess, but let me know if you have already
> >         checked this or if this is not the issue.
> >
> >         Lance
> >
> >         raiderdav wrote:
> >         > Configuration:
> >         >   Trac 0.11.4
> >         >   SVN 1.5.6 (r36142)
> >         >   Python 2.5.4
> >         >   Apache 2.2.11
> >         >   Windows Small Business Server 2008
> >         >
> >         > I'm installing Trac for the first time on this server, and
> >         am having
> >         > issues connecting to the SVN repository.  I believe I have
> >         the Trac
> >         > environment established successfully, and can connect via
> >         Apache using
> >         > the mod_wsgi approach with the repository_dir cleared.
> >         >
> >         > With my Trac.ini file set with the following I can view the
> >         generic
> >         > "Welcome to Trac" page and local documentation:
> >         >    repository_dir =
> >         >    repository_type = svn
> >         >
> >         > When I change it to
> >         >      repository_dir = c:\svn\ltm
> >         > the Trac URL is no longer accessible and I get a "Connection
> >         > Interrupted. The connection to the server was reset while
> >         the page was
> >         > loading." in the browser.  I turned on debug logging to
> >         file, and the
> >         > last line of the log reads:
> >         >
> >         >    2009-06-02 14:25:03,322 Trac[main] DEBUG: Dispatching
> >         <Request "GET
> >         > u''">
> >         >
> >         >
> >         > With the repository_dir set with the correct path, I can run
> >         trac-
> >         > admin resync and the repository history counts through all 292
> >         > revisions successfully.  This leads me to believe that the
> >         connection
> >         > to SVN is established properly, but I still can't view
> >         anything with
> >         > the repository path included.
> >         >
> >         > Any ideas on what to check or test next?
> >         >
> >         > Thanks - Dave
> >         >
> >         > >
> >         >
> >
> >
> >
> >
> >
> >
> > >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to