Re: test issues

["Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem" <root@doctor.nl2k.ab.ca>]

On Sun, Jun 25, 2006 at 06:10:07AM -0600, Dave Shariff Yadallee -  System Administrator a.k.a. The Root of the Problem wrote:
> On Sun, Jun 25, 2006 at 02:12:38PM +0200, Pierangelo Masarati wrote:
> > On Sun, 2006-06-25 at 05:44 -0600, Dave Shariff Yadallee - System
> > Administrator a.k.a. The Root of the Problem wrote:
> > > On Sun, Jun 25, 2006 at 08:40:06AM +0200, Pierangelo Masarati wrote:
> > > > 
> > > > > Why is this not working?
> > > > 
> > > > See <http://www.openldap.org/faq/data/cache/1089.html>.
> > > > 
> > > > p.
> > > > 
> > > >
> > > 
> > > 
> > > Upon following that link this is what I get:
> > 
> > The intention of the contents of that link was to make you __find__ the
> > log file and then __read__ its contents, not just cut'n'paste it into a
> > message so that someone else reads it for you.  The relevant portion is
> > 
> > > bdb(o=OpenLDAP Project,l=Internet): Berkeley DB library configured to support only private environments
> > > bdb_db_open: Database cannot be opened, err 22. Restore from backup!
> > > ====> bdb_cache_release_all
> > > bdb(o=OpenLDAP Project,l=Internet): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
> > > bdb(o=OpenLDAP Project,l=Internet): txn_checkpoint interface requires an environment configured for the transaction subsystem
> > > bdb_db_close: txn_checkpoint failed: Invalid argument (22)

Now I get 

backend_startup_one: starting "o=OpenLDAP Project,l=Internet"
bdb_db_open: o=OpenLDAP Project,l=Internet
bdb_db_open: Warning - No DB_CONFIG file found in directory ./testrun/db.1.a: (2
)
Expect poor performance for suffix o=OpenLDAP Project,l=Internet.
bdb_db_open: dbenv_open(./testrun/db.1.a)
bdb(o=OpenLDAP Project,l=Internet): Berkeley DB library configured to support on
ly private environments
bdb_db_open: Database cannot be opened, err 22. Restore from backup!
====> bdb_cache_release_all
bdb(o=OpenLDAP Project,l=Internet): DB_ENV->lock_id_free interface requires an e
nvironment configured for the locking subsystem
bdb(o=OpenLDAP Project,l=Internet): txn_checkpoint interface requires an environ
ment configured for the transaction subsystem
bdb_db_close: txn_checkpoint failed: Invalid argument (22)
backend_startup_one: bi_db_open failed! (22)
lt-slapd shutdown: initiated
====> bdb_cache_release_all
bdb_db_close: alock_close failed
lt-slapd destroy: freeing system resources.
slapd stopped.
connections_destroy: nothing to destroy.  

ANd I did look at testrun/db.1.a/ and there is only an ALOCK.

> > 
> > which shows that either your build of Berkeley DB is screwed, or, if you
> > didn't build it yourself, the packaged version you're using is screwed. 
> > 
> > This occurred to many users in the past, and it has already been
> > discussed on the openldap-software list; I don't remember the results of
> > those discussions, because I always build Berkeley myself and I never
> > got into that.
> > 
> > Please search thrugh the archives for a reasonable solution to this
> > issue.
> >
> 
> I build from source.
> 
> There is a possibility of a cross connect.
> 
> I did have db-4.4 but did just junk this since it
> could not work with Sendmail 8.13 and hence
> dropped back to db - 4.3 which are working with Sendmail 8.13
> and Apache 2.0.X .
>  
> > p.
> > 
> > 
> > 
> > 
> > Ing. Pierangelo Masarati
> > Responsabile Open Solution
> > OpenLDAP Core Team
> > 
> > SysNet s.n.c.
> > Via Dossi, 8 - 27100 Pavia - ITALIA
> > http://www.sys-net.it
> > ------------------------------------------
> > Office:   +39.02.23998309          
> > Mobile:   +39.333.4963172
> > Email:    pierangelo.masarati@sys-net.it
> > ------------------------------------------
> > 
> > 
> > -- 
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.