So should I go ahead and submit a ticket for this on Trac that there is an
incompatibility between Trac 0.11.4, Apache 2.2.x and Python 2.5 on Windows?


On Tue, Jun 9, 2009 at 4:53 PM, David Headley <[email protected]> wrote:

> I got some help from the Apache mailing list, and apparently there is a
> version mismatch issue involving the libapr.dll file.
>
> Under Python25\Lib\site-packages\libsvn, there is a file named libapr.dll
> that is version 0.9.17.0. This is the file version that is referenced in my
> event viewer when Apache crashes.
> Under Apache2.2\bin there is libapr-1.dll and it is version 1.3.3.0.
>
> Similarly, the other .dlls don't match that are in the Python libsvn (ie
> libapriconv and libaprutil).
>
> I tried copying the new DLL files from Apache\bin into the libsvn folder
> and renaming them without the "-1" but that did not work properly.  The Trac
> URL no longer crashes Apache, but I get an error when I try to run a
> Trac-Admin resync:
> *   The procedure entry point _apr _socket_cre...@16 could not be located
> in the dynamic link library libapr.dll*
>
> Apparently the newer version of the DLLs don't have same internal function
> calls - is there any way to workaround this?  From the Apache mailing list "
> *Apache 2.2.x and SVN work with APR 1.x.  The old APR 0.9.x exists for
> Apache 2.0.*"
>
> 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
>> >
>> >
>>
>

--~--~---------~--~----~------------~-------~--~----~
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