WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: xen, tls, futex locks and berkley db

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: xen, tls, futex locks and berkley db
From: Robin Green <greenrd@xxxxxxxxxxxxx>
Date: Thu, 28 Apr 2005 03:55:08 +0100
Delivery-date: Thu, 28 Apr 2005 02:55:04 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1114502815.4707.15.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Pan/0.14.2.91 (As She Crawled Across the Table)
On Tue, 26 Apr 2005 10:06:55 +0200, Filip Sergeys wrote:

> I ran into a problem which I don't know how to solve.
> In order for xen to run in maximum performance, tls should be disabled.
> However on that machine I want to run openldap with berkley db backend.
> When openldap is started; I get the following error:
> 
> bdb_db_open: dbenv_open failed: Function not implemented (38)
> slapd[8218]: backend_startup: bi_db_open(0) failed! (38)
> slapd[8218]: bdb(dc=eccent,dc=be): DB_ENV->lock_id_free interface
> requires an environment configured for the locking subsystem
> slapd[8218]: bdb(dc=eccent,dc=be): txn_checkpoint interface requires an
> environment configured for the transaction subsystem
> slapd[8218]: bdb_db_destroy: txn_checkpoint failed: Invalid argument
> (22)

What I did to get around this issue, was move our data over to a
postgresql backend. It took a couple of days but it's now basically
working. If anyone would like help transitioning to a postgresql backend
for openldap, please get in touch off-list and I'd be happy to help.
-- 
Robin


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>