Howard Wilkinson
2008-Jul-29 08:51 UTC
[Fedora-directory-users] Recover directory database files when disk fills up!
We had the disk with the directory database files fill up overnight, a
rogue process :-[
Now the directory server will not start I get the following reported in
the system logs.
Jul 29 09:44:50 bastion ns-slapd: auxpropfunc error invalid
parameter supplied
Jul 29 09:44:50 bastion ns-slapd: sql_select option missing
Jul 29 09:44:50 bastion ns-slapd: auxpropfunc error no mechanism
available
What can I do to recover the database so that I can start the server?
Richard Megginson
2008-Jul-29 14:47 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Howard Wilkinson wrote:> We had the disk with the directory database files fill up overnight, a > rogue process :-[ > > Now the directory server will not start I get the following reported > in the system logs. > > Jul 29 09:44:50 bastion ns-slapd: auxpropfunc error invalid > parameter supplied > Jul 29 09:44:50 bastion ns-slapd: sql_select option missing > Jul 29 09:44:50 bastion ns-slapd: auxpropfunc error no mechanism > available >These are messages from sasl. I believe you can ignore them, I don''t think they have anything to do with the problem.> > > What can I do to recover the database so that I can start the server?What messages do you get in the directory server error log?> > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >
Howard Wilkinson
2008-Aug-04 09:44 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Richard Megginson wrote:> Howard Wilkinson wrote: >> > These are messages from sasl. I believe you can ignore them, I don''t > think they have anything to do with the problem. >> >> >> What can I do to recover the database so that I can start the server? > What messages do you get in the directory server error log?Fedora-Directory/1.1.1 B2008.151.1915 bastion.finsbury.cohtech.co.uk:636 (/etc/dirsrv/slapd-bastion) [04/Aug/2008:10:40:15 +0100] - Fedora-Directory/1.1.1 B2008.151.1915 starting up [04/Aug/2008:10:40:15 +0100] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [04/Aug/2008:10:40:17 +0100] - libdb: file userRoot/id2entry.db4 has LSN 518/7178886, past end of log at 1/4431 [04/Aug/2008:10:40:17 +0100] - libdb: Commonly caused by moving a database from one database environment [04/Aug/2008:10:40:17 +0100] - libdb: to another without clearing the database LSNs, or by removing all of [04/Aug/2008:10:40:17 +0100] - libdb: the log files from a database environment [04/Aug/2008:10:40:17 +0100] - libdb: /var/lib/dirsrv/slapd-bastion/db/userRoot/id2entry.db4: unexpected file type or format [04/Aug/2008:10:40:17 +0100] - dbp->open("userRoot/id2entry.db4") failed: Invalid argument (22) [04/Aug/2008:10:40:17 +0100] - dblayer_instance_start fail: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - libdb: file NetscapeRoot/id2entry.db4 has LSN 210/949652, past end of log at 1/6026 [04/Aug/2008:10:40:18 +0100] - libdb: Commonly caused by moving a database from one database environment [04/Aug/2008:10:40:18 +0100] - libdb: to another without clearing the database LSNs, or by removing all of [04/Aug/2008:10:40:18 +0100] - libdb: the log files from a database environment [04/Aug/2008:10:40:18 +0100] - libdb: /var/lib/dirsrv/slapd-bastion/db/NetscapeRoot/id2entry.db4: unexpected file type or format [04/Aug/2008:10:40:18 +0100] - dbp->open("NetscapeRoot/id2entry.db4") failed: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - dblayer_instance_start fail: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - libdb: file cohtechNet/id2entry.db4 has LSN 400/7475236, past end of log at 1/6478 [04/Aug/2008:10:40:18 +0100] - libdb: Commonly caused by moving a database from one database environment [04/Aug/2008:10:40:18 +0100] - libdb: to another without clearing the database LSNs, or by removing all of [04/Aug/2008:10:40:18 +0100] - libdb: the log files from a database environment [04/Aug/2008:10:40:18 +0100] - libdb: /var/lib/dirsrv/slapd-bastion/db/cohtechNet/id2entry.db4: unexpected file type or format [04/Aug/2008:10:40:18 +0100] - dbp->open("cohtechNet/id2entry.db4") failed: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - dblayer_instance_start fail: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - libdb: file cohtechCom/id2entry.db4 has LSN 198/9190421, past end of log at 1/6478 [04/Aug/2008:10:40:18 +0100] - libdb: Commonly caused by moving a database from one database environment [04/Aug/2008:10:40:18 +0100] - libdb: to another without clearing the database LSNs, or by removing all of [04/Aug/2008:10:40:18 +0100] - libdb: the log files from a database environment [04/Aug/2008:10:40:18 +0100] - libdb: /var/lib/dirsrv/slapd-bastion/db/cohtechCom/id2entry.db4: unexpected file type or format [04/Aug/2008:10:40:18 +0100] - dbp->open("cohtechCom/id2entry.db4") failed: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - dblayer_instance_start fail: Invalid argument (22) [04/Aug/2008:10:40:18 +0100] - WARNING---no write permission to file /var/lib/dirsrv/slapd-bastion/db/cohCoUk/log.0000000001 [04/Aug/2008:10:40:18 +0100] - start: Failed to start databases, err=22 Invalid argument [04/Aug/2008:10:40:18 +0100] - Failed to allocate 10000000 byte dbcache. Please reduce nsslapd-cache-autosize and Restart the server. [04/Aug/2008:10:40:18 +0100] - Failed to start database plugin ldbm database [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance willertonCohtechNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance viaFonCohtechNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance userRoot already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance towerbridgeCohtechNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance time2joininCohtechNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance sudaminltdCom already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance stokieCohtechCoUk already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance seamsysCom already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance palmPrintsCom already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance orbItNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance orbItCom already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance orbCoUk already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance NetscapeRoot already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance finsburyCohtechCoUk already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance conceptsIntCohtechNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohtechOrg already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohtechNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohtechCom already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance coherentTechnologyOrg already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance coherentTechnologyNet already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance coherentTechnologyCoUk already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance coherentTechnologyCom already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance coherentLocal already exists [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohCoUk already exists [04/Aug/2008:10:40:18 +0100] binder-based resource limits - nsLookThroughLimit: parameter error (slapi_reslimit_register() already registered) [04/Aug/2008:10:40:18 +0100] - start: Resource limit registration failed [04/Aug/2008:10:40:18 +0100] - Failed to start database plugin ldbm database [04/Aug/2008:10:40:18 +0100] - Error: Failed to resolve plugin dependencies [04/Aug/2008:10:40:18 +0100] - Error: accesscontrol plugin ACL Plugin is not started [04/Aug/2008:10:40:18 +0100] - Error: preoperation plugin ACL preoperation is not started [04/Aug/2008:10:40:18 +0100] - Error: object plugin Class of Service is not started [04/Aug/2008:10:40:18 +0100] - Error: preoperation plugin HTTP Client is not started [04/Aug/2008:10:40:18 +0100] - Error: database plugin ldbm database is not started [04/Aug/2008:10:40:18 +0100] - Error: object plugin Legacy Replication Plugin is not started [04/Aug/2008:10:40:19 +0100] - Error: object plugin Multimaster Replication Plugin is not started [04/Aug/2008:10:40:19 +0100] - Error: object plugin Roles Plugin is not started [04/Aug/2008:10:40:19 +0100] - Error: object plugin Views is not started
Rich Megginson
2008-Aug-04 14:28 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Howard Wilkinson wrote:> Richard Megginson wrote: >> Howard Wilkinson wrote: >>> >> These are messages from sasl. I believe you can ignore them, I don''t >> think they have anything to do with the problem. >>> >>> >>> What can I do to recover the database so that I can start the server? >> What messages do you get in the directory server error log? > > Fedora-Directory/1.1.1 B2008.151.1915 > bastion.finsbury.cohtech.co.uk:636 (/etc/dirsrv/slapd-bastion) > > [04/Aug/2008:10:40:15 +0100] - Fedora-Directory/1.1.1 > B2008.151.1915 starting up > [04/Aug/2008:10:40:15 +0100] - Detected Disorderly Shutdown last > time Directory Server was running, recovering database. > [04/Aug/2008:10:40:17 +0100] - libdb: file userRoot/id2entry.db4 > has LSN 518/7178886, past end of log at 1/4431 > [04/Aug/2008:10:40:17 +0100] - libdb: Commonly caused by moving a > database from one database environment > [04/Aug/2008:10:40:17 +0100] - libdb: to another without clearing > the database LSNs, or by removing all of > [04/Aug/2008:10:40:17 +0100] - libdb: the log files from a > database environment >How did you create the backup?> > [04/Aug/2008:10:40:17 +0100] - libdb: > /var/lib/dirsrv/slapd-bastion/db/userRoot/id2entry.db4: unexpected > file type or format > [04/Aug/2008:10:40:17 +0100] - dbp->open("userRoot/id2entry.db4") > failed: Invalid argument (22) > [04/Aug/2008:10:40:17 +0100] - dblayer_instance_start fail: > Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - libdb: file > NetscapeRoot/id2entry.db4 has LSN 210/949652, past end of log at > 1/6026 > [04/Aug/2008:10:40:18 +0100] - libdb: Commonly caused by moving a > database from one database environment > [04/Aug/2008:10:40:18 +0100] - libdb: to another without clearing > the database LSNs, or by removing all of > [04/Aug/2008:10:40:18 +0100] - libdb: the log files from a > database environment > [04/Aug/2008:10:40:18 +0100] - libdb: > /var/lib/dirsrv/slapd-bastion/db/NetscapeRoot/id2entry.db4: > unexpected file type or format > [04/Aug/2008:10:40:18 +0100] - > dbp->open("NetscapeRoot/id2entry.db4") failed: Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - dblayer_instance_start fail: > Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - libdb: file cohtechNet/id2entry.db4 > has LSN 400/7475236, past end of log at 1/6478 > [04/Aug/2008:10:40:18 +0100] - libdb: Commonly caused by moving a > database from one database environment > [04/Aug/2008:10:40:18 +0100] - libdb: to another without clearing > the database LSNs, or by removing all of > [04/Aug/2008:10:40:18 +0100] - libdb: the log files from a > database environment > [04/Aug/2008:10:40:18 +0100] - libdb: > /var/lib/dirsrv/slapd-bastion/db/cohtechNet/id2entry.db4: > unexpected file type or format > [04/Aug/2008:10:40:18 +0100] - > dbp->open("cohtechNet/id2entry.db4") failed: Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - dblayer_instance_start fail: > Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - libdb: file cohtechCom/id2entry.db4 > has LSN 198/9190421, past end of log at 1/6478 > [04/Aug/2008:10:40:18 +0100] - libdb: Commonly caused by moving a > database from one database environment > [04/Aug/2008:10:40:18 +0100] - libdb: to another without clearing > the database LSNs, or by removing all of > [04/Aug/2008:10:40:18 +0100] - libdb: the log files from a > database environment > [04/Aug/2008:10:40:18 +0100] - libdb: > /var/lib/dirsrv/slapd-bastion/db/cohtechCom/id2entry.db4: > unexpected file type or format > [04/Aug/2008:10:40:18 +0100] - > dbp->open("cohtechCom/id2entry.db4") failed: Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - dblayer_instance_start fail: > Invalid argument (22) > [04/Aug/2008:10:40:18 +0100] - WARNING---no write permission to > file /var/lib/dirsrv/slapd-bastion/db/cohCoUk/log.0000000001 > [04/Aug/2008:10:40:18 +0100] - start: Failed to start databases, > err=22 Invalid argument > [04/Aug/2008:10:40:18 +0100] - Failed to allocate 10000000 byte > dbcache. Please reduce nsslapd-cache-autosize and Restart the server. > [04/Aug/2008:10:40:18 +0100] - Failed to start database plugin > ldbm database > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > willertonCohtechNet already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > viaFonCohtechNet already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance userRoot > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > towerbridgeCohtechNet already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > time2joininCohtechNet already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > sudaminltdCom already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > stokieCohtechCoUk already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance seamsysCom > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > palmPrintsCom already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance orbItNet > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance orbItCom > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance orbCoUk > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance NetscapeRoot > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > finsburyCohtechCoUk already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > conceptsIntCohtechNet already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohtechOrg > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohtechNet > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohtechCom > already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > coherentTechnologyOrg already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > coherentTechnologyNet already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > coherentTechnologyCoUk already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > coherentTechnologyCom already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance > coherentLocal already exists > [04/Aug/2008:10:40:18 +0100] - WARNING: ldbm instance cohCoUk > already exists > [04/Aug/2008:10:40:18 +0100] binder-based resource limits - > nsLookThroughLimit: parameter error (slapi_reslimit_register() > already registered) > [04/Aug/2008:10:40:18 +0100] - start: Resource limit registration > failed > [04/Aug/2008:10:40:18 +0100] - Failed to start database plugin > ldbm database > [04/Aug/2008:10:40:18 +0100] - Error: Failed to resolve plugin > dependencies > [04/Aug/2008:10:40:18 +0100] - Error: accesscontrol plugin ACL > Plugin is not started > [04/Aug/2008:10:40:18 +0100] - Error: preoperation plugin ACL > preoperation is not started > [04/Aug/2008:10:40:18 +0100] - Error: object plugin Class of > Service is not started > [04/Aug/2008:10:40:18 +0100] - Error: preoperation plugin HTTP > Client is not started > [04/Aug/2008:10:40:18 +0100] - Error: database plugin ldbm > database is not started > [04/Aug/2008:10:40:18 +0100] - Error: object plugin Legacy > Replication Plugin is not started > [04/Aug/2008:10:40:19 +0100] - Error: object plugin Multimaster > Replication Plugin is not started > [04/Aug/2008:10:40:19 +0100] - Error: object plugin Roles Plugin > is not started > [04/Aug/2008:10:40:19 +0100] - Error: object plugin Views is not > started > > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >
Howard Wilkinson
2008-Aug-04 15:02 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Rich Megginson wrote:> Howard Wilkinson wrote: >> Richard Megginson wrote: >>> Howard Wilkinson wrote: >>>> >>> These are messages from sasl. I believe you can ignore them, I >>> don''t think they have anything to do with the problem. >>>> >>>> >>>> What can I do to recover the database so that I can start the server? >>> What messages do you get in the directory server error log? >> >> Fedora-Directory/1.1.1 B2008.151.1915 >> bastion.finsbury.cohtech.co.uk:636 (/etc/dirsrv/slapd-bastion) >> >> [04/Aug/2008:10:40:15 +0100] - Fedora-Directory/1.1.1 >> B2008.151.1915 starting up >> [04/Aug/2008:10:40:15 +0100] - Detected Disorderly Shutdown last >> time Directory Server was running, recovering database. >> [04/Aug/2008:10:40:17 +0100] - libdb: file userRoot/id2entry.db4 >> has LSN 518/7178886, past end of log at 1/4431 >> [04/Aug/2008:10:40:17 +0100] - libdb: Commonly caused by moving a >> database from one database environment >> [04/Aug/2008:10:40:17 +0100] - libdb: to another without clearing >> the database LSNs, or by removing all of >> [04/Aug/2008:10:40:17 +0100] - libdb: the log files from a >> database environment >> > How did you create the backup?[Snip] There was no backup created. The system ran out of disk space in the log partition and in the database partition during an OS upgrade. It looks ike the version of db4 has changed and the directory server failed while this was happening. I would like to recover by rolling forward if possible, but if not this is a multi-master instance and I can probably rebuild if I have to. Howard.
Rich Megginson
2008-Aug-04 15:25 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Howard Wilkinson wrote:> Rich Megginson wrote: >> Howard Wilkinson wrote: >>> Richard Megginson wrote: >>>> Howard Wilkinson wrote: >>>>> >>>> These are messages from sasl. I believe you can ignore them, I >>>> don''t think they have anything to do with the problem. >>>>> >>>>> >>>>> What can I do to recover the database so that I can start the server? >>>> What messages do you get in the directory server error log? >>> >>> Fedora-Directory/1.1.1 B2008.151.1915 >>> bastion.finsbury.cohtech.co.uk:636 (/etc/dirsrv/slapd-bastion) >>> >>> [04/Aug/2008:10:40:15 +0100] - Fedora-Directory/1.1.1 >>> B2008.151.1915 starting up >>> [04/Aug/2008:10:40:15 +0100] - Detected Disorderly Shutdown last >>> time Directory Server was running, recovering database. >>> [04/Aug/2008:10:40:17 +0100] - libdb: file userRoot/id2entry.db4 >>> has LSN 518/7178886, past end of log at 1/4431 >>> [04/Aug/2008:10:40:17 +0100] - libdb: Commonly caused by moving a >>> database from one database environment >>> [04/Aug/2008:10:40:17 +0100] - libdb: to another without clearing >>> the database LSNs, or by removing all of >>> [04/Aug/2008:10:40:17 +0100] - libdb: the log files from a >>> database environment >>> >> How did you create the backup? > > [Snip] > > There was no backup created. The system ran out of disk space in the > log partition and in the database partition during an OS upgrade. It > looks ike the version of db4 has changed and the directory server > failed while this was happening. I would like to recover by rolling > forward if possible, but if not this is a multi-master instance and I > can probably rebuild if I have to.Ok, I see. I''m not sure if directory server auto-recovery is possible with this sort of failure. You might be able to use the berkeley db command line utilities to upgrade and/or recover your database files. http://www.oracle.com/technology/documentation/berkeley-db/db/utility/index.html - you may have to figure out which version of bdb you are using, then find the appropriate documentation - rpm -qi db4 or rpm -qi db4-utils. You might try db2ldif to export your data, then re-import using ldif2db, but that would force a replication re-init anyway.> > Howard. > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users
Howard Wilkinson
2008-Aug-06 09:30 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Rich Megginson wrote: [Snip]> Ok, I see. I''m not sure if directory server auto-recovery is possible > with this sort of failure. You might be able to use the berkeley db > command line utilities to upgrade and/or recover your database files. > http://www.oracle.com/technology/documentation/berkeley-db/db/utility/index.html > - you may have to figure out which version of bdb you are using, then > find the appropriate documentation - rpm -qi db4 or rpm -qi db4-utils. > You might try db2ldif to export your data, then re-import using > ldif2db, but that would force a replication re-init anyway.I have rebuilt the system and reinitialised the roots from the other multi-master. The directory server looks as though it is working properly and I can connect to the admin server from one of the other machines that is running the older version of the code (fedora-idm-console) but if I run the same command on the restored box then it will not do anything just sits there having typed in the command. How do I diagnose and fix this? Howard.
Rich Megginson
2008-Aug-06 13:26 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Howard Wilkinson wrote:> Rich Megginson wrote: > > [Snip] >> Ok, I see. I''m not sure if directory server auto-recovery is >> possible with this sort of failure. You might be able to use the >> berkeley db command line utilities to upgrade and/or recover your >> database files. >> http://www.oracle.com/technology/documentation/berkeley-db/db/utility/index.html >> - you may have to figure out which version of bdb you are using, then >> find the appropriate documentation - rpm -qi db4 or rpm -qi db4-utils. >> You might try db2ldif to export your data, then re-import using >> ldif2db, but that would force a replication re-init anyway. > I have rebuilt the system and reinitialised the roots from the other > multi-master. The directory server looks as though it is working > properly and I can connect to the admin server from one of the other > machines that is running the older version of the code > (fedora-idm-console) but if I run the same command on the restored box > then it will not do anything just sits there having typed in the command.fedora-idm-console -D 9 -f console.log - does that show anything?> How do I diagnose and fix this? > > Howard. > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users
Howard Wilkinson
2008-Nov-17 16:07 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Finally got back to diagnosing the problem with the console and behold
the behaviour has changed. Still not working right but I am now getting
3 slightly different failures depending on which server I try to connect to.
1. Connecting to rebuilt directory server when I look at the
encryption tab for the server configuration I get a pop up failure
that says ''SSL related initialization failed''. After
pressing OK
the tab fills in correctly and the error does not reappear until I
reopen the server.
2. Connecting to the rebuilt administration server and select the
Configuration tab I get the same error message as a pop up. When I
press OK the window show ''failed to load data''.
3. Connecting to another administration server from our Multi-master
farm I get the error message on the Configuration Tab - ''no
protocol: admin-server/tasks/Sonfiguration/ServerSetup'' and again
''failed to load data'' after pressing OK.
The debug console logs are attached fro each case.
No errors are reported in the logs for the admin servers.
Where do I look next?
Howard.
Rich Megginson
2008-Nov-18 15:51 UTC
Re: [Fedora-directory-users] Recover directory database files when disk fills up!
Howard Wilkinson wrote:> Finally got back to diagnosing the problem with the console and behold > the behaviour has changed. Still not working right but I am now > getting 3 slightly different failures depending on which server I try > to connect to. > > 1. Connecting to rebuilt directory server when I look at the > encryption tab for the server configuration I get a pop up > failure that says ''SSL related initialization failed''. After > pressing OK the tab fills in correctly and the error does not > reappear until I reopen the server. > 2. Connecting to the rebuilt administration server and select the > Configuration tab I get the same error message as a pop up. When > I press OK the window show ''failed to load data''. > 3. Connecting to another administration server from our > Multi-master farm I get the error message on the Configuration > Tab - ''no protocol: > admin-server/tasks/Sonfiguration/ServerSetup'' and again ''failed > to load data'' after pressing OK. >What is happening is that the console invokes a CGI via the admin server to create and/or manage those files. The following permissions are required: The admin server user id (default: nobody - grep User /etc/dirsrv/admin-serv/console.conf to see what the userid is) must have permission to create new files in /etc/dirsrv/slapd-instancename and /etc/dirsrv/admin-serv, and read and write cert8.db, key3.db, and secmod.db in those directories. If you need/want to run the directory server and the admin server as different users, then you should create a group to which both of those users belong (and no other users) - you will need to make sure those files and directories have the appropriate group permissions, since the directory server needs to read/write files in /etc/dirsrv/slapd-instancename as well as the admin server.> The debug console logs are attached fro each case. > > No errors are reported in the logs for the admin servers. > > Where do I look next? > > Howard. > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >