[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Need information on alock file in data directory of OpenLDAP 2.4.39



Thanks for the information.
I am able get rid of the slapcat hanging by your suggestion but not fully I guess
whenever I restart the system I get the below error,again alock trouble
 
5454b6be bdb_db_open: database "dc=example,dc=com": alock_recover failed
5454b6be ====> bdb_cache_release_all
 
Regards,
Pramod

On Fri, Oct 31, 2014 at 2:13 PM, Howard Chu <hyc@symas.com> wrote:
Sergio NNX wrote:
 > > I see somewhere code hangs in the alock.c file I think the slapcat
 > > process not able to grab the lock,is it correct? or something
 > > different.

Ciao.

The same issue seems to occur under Windows. I reckon I may have reported it
some time ago.

Windows locking was fixed in ITS#7361, in 2.4.33, 2 years ago.


...
...
52879a45 bdb_db_open: "dc=example,dc=com"
52879a45 bdb_db_open: database "dc=example,dc=com": unclean shutdown detected;
attempting recovery.
52879a45 bdb_db_open: warning - no DB_CONFIG file found in directory
../testrun/db.1.a: (2).
Expect poor performance for suffix "dc=example,dc=com".
52879a45 bdb_db_open: database "dc=example,dc=com": dbenv_open(../testrun/db.1.a).
52879a46 bdb_db_open: database "dc=example,dc=com": alock_recover failed
52879a46 ====> bdb_cache_release_all
52879a46 bdb_db_close: database "dc=example,dc=com": alock_close failed
52879a46 backend_startup_one (type=bdb, suffix="dc=example,dc=com"):
bi_db_open failed! (-1)
52879a46 slapd shutdown: initiated
52879a46 ====> bdb_cache_release_all
52879a46 bdb_db_close: database "dc=example,dc=com": alock_close failed
52879a46 slapd destroy: freeing system resources.
52879a46 slapd stopped.
...
...


--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/