Home › Forums › OS X Server and Client Discussion › Open Directory › Open Directory Failure after updating leopard server
- This topic has 0 replies, 1 voice, and was last updated 17 years, 10 months ago by
myrkatt.
-
AuthorPosts
-
January 11, 2009 at 1:25 pm #375115
myrkatt
ParticipantI’m running Xserver 10.5.4 on an Intel Xserve. Upgraded last month to this version (was on 10.5.2). Since then the Open Directory Service has stopped and the postfix has gone weird (I think related since I was running virtual boxes pointing at Open Directory users)
In Workgroup Manager – trying to Authenticate to the LDAP node produces the error: “Error of type eDSOpenNodeFailure (-14002) on line 3909 of /Source/WorkgroupManager/WorkgroupManager-319.1.1/PMMUGMainView.mm”
In /var/log/slapd the following recurs:
@(#) $OpenLDAP: slapd 2.3.27 (Jul 15 2008 11:24:25) $
Jan 11 13:08:08 exapia slapd[981]: overlay_config(): warning, overlay “dynid” already in list
Jan 11 13:08:08: — last message repeated 4 times —
Jan 11 13:08:08 exapia slapd[981]: bdb_db_open: unclean shutdown detected; attempting recovery.
Jan 11 13:08:08 exapia slapd[981]: bdb(dc=exapia,dc=co,dc=uk): Log sequence error: page LSN 1 351468; previous LSN 2 3482050
Jan 11 13:08:08 exapia slapd[981]: bdb(dc=exapia,dc=co,dc=uk): Recovery function for LSN 1 930 failed on forward pass
Jan 11 13:08:08 exapia slapd[981]: bdb(dc=exapia,dc=co,dc=uk): PANIC: Invalid argument
Jan 11 13:08:08 exapia slapd[981]: bdb(dc=exapia,dc=co,dc=uk): PANIC: fatal region error detected; run recovery
Jan 11 13:08:10: — last message repeated 13 times —
Jan 11 13:08:10 exapia slapd[981]: bdb_db_open: Database cannot be recovered, err -30978. Restore from backup!
Jan 11 13:08:10 exapia slapd[981]: bdb(dc=exapia,dc=co,dc=uk): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
Jan 11 13:08:10 exapia slapd[981]: bdb(dc=exapia,dc=co,dc=uk): txn_checkpoint interface requires an environment configured for the transaction subsystem
Jan 11 13:08:10 exapia slapd[981]: bdb_db_close: txn_checkpoint failed: Invalid argument (22)
Jan 11 13:08:10 exapia slapd[981]: backend_startup_one: bi_db_open failed! (-30978)
Jan 11 13:08:10 exapia slapd[981]: bdb_db_close: alock_close failed
Jan 11 13:08:10 exapia slapd[981]: slapd stopped.
Jan 11 13:08:10 exapia slapd[981]: connections_destroy: nothing to destroy.
Jan 11 13:08:19 exapia slapd[990]: @(#) $OpenLDAP: slapd 2.3.27 (Jul 15 2008 11:24:25) $
Jan 11 13:08:19 exapia slapd[990]: overlay_config(): warning, overlay “dynid” already in list
Jan 11 13:08:19: — last message repeated 4 times —
Jan 11 13:08:19 exapia slapd[990]: bdb_db_open: unclean shutdown detected; attempting recovery.
Jan 11 13:08:19 exapia slapd[990]: bdb(dc=exapia,dc=co,dc=uk): Log sequence error: page LSN 1 351468; previous LSN 2 3482050
Jan 11 13:08:19 exapia slapd[990]: bdb(dc=exapia,dc=co,dc=uk): Recovery function for LSN 1 930 failed on forward pass
Jan 11 13:08:19 exapia slapd[990]: bdb(dc=exapia,dc=co,dc=uk): PANIC: Invalid argument
Jan 11 13:08:19 exapia slapd[990]: bdb(dc=exapia,dc=co,dc=uk): PANIC: fatal region error detected; run recovery
Jan 11 13:08:20: — last message repeated 13 times —
Jan 11 13:08:20 exapia slapd[990]: bdb_db_open: Database cannot be recovered, err -30978. Restore from backup!
Jan 11 13:08:20 exapia slapd[990]: bdb(dc=exapia,dc=co,dc=uk): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
Jan 11 13:08:20 exapia slapd[990]: bdb(dc=exapia,dc=co,dc=uk): txn_checkpoint interface requires an environment configured for the transaction subsystem
Jan 11 13:08:20 exapia slapd[990]: bdb_db_close: txn_checkpoint failed: Invalid argument (22)
Jan 11 13:08:20 exapia slapd[990]: backend_startup_one: bi_db_open failed! (-30978)
Jan 11 13:08:20 exapia slapd[990]: bdb_db_close: alock_close failed
Jan 11 13:08:20 exapia slapd[990]: slapd stopped.
Jan 11 13:08:20 exapia slapd[990]: connections_destroy: nothing to destroy.This looks like a possible disk corruption – if so, how do I rebuild the LDAP service once the disk is repaired?
On the other hand, has anyone else had this problem and is there a less drastic solution?
Thanks for your help
Myrkatt
-
AuthorPosts
- You must be logged in to reply to this topic.