Unsupported version control system "svn": "libsvn_client-1.so.1: failed to map segment from shared object: Cannot allocate memory"

[anonymous]

Hello

OS: Debian Lenny x86_64

aptitude search svn subversion |grep ^i
i A libsvn-perl                     - Perl bindings for Subversion
i A libsvn1                         - Shared libraries used by Subversion
i A python-subversion               - Python bindings for Subversion
i   python-svn                      - A(nother) Python interface to Subversion
i A subversion                      - Advanced version control system
i   subversion-tools                - Assorted tools related to Subversion

svn --version
svn, version 1.5.1 (r32289)
[...]

I installed trac with "easy_install Trac" and I get a error message when I access trac

Warning: Can't synchronize with the repository (Unsupported version control system "svn": "libsvn_client-1.so.1: failed to map segment from shared object: Cannot allocate memory" ). Look in the Trac log for more information.

Trac Error
Unsupported version control system "svn": "libsvn_client-1.so.1: failed to map segment from shared object: Cannot allocate memory"

trac.log

[...]
2009-07-18 19:16:36,553 Trac[svn_fs] INFO: Failed to load Subversion bindings
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/Trac-0.11.5rc2-py2.5.egg/trac/versioncontrol/svn_fs.py", line 256, in __init__
    _import_svn()
  File "/usr/lib/python2.5/site-packages/Trac-0.11.5rc2-py2.5.egg/trac/versioncontrol/svn_fs.py", line 71, in _import_svn
    from svn import fs, repos, core, delta
  File "/var/lib/python-support/python2.5/svn/fs.py", line 19, in <module>
    from libsvn.fs import *
  File "/var/lib/python-support/python2.5/libsvn/fs.py", line 7, in <module>
    import _fs
ImportError: libsvn_client-1.so.1: failed to map segment from shared object: Cannot allocate memory
[...]

[anonymous]

trac.log

[Emmanuel Blot]

This error is not related to Trac, but to the SVN python bindings.

I'd suggest you post a message to the MailingList to see if other users have encountered the same error, although the error message looks like a out-of-memory error on your machine.

You may want to check your server memory status.

I've been running a similar configuration for months (Debian Lenny x86_64) with no issue.