Re: [389-users] dirsrv does not start anymore

2012-03-06 Thread Rich Megginson
On 03/06/2012 09:58 AM, Vasil Mikhalenya wrote: Import of ldif file solved the problem. /usr/lib64/dirsrv/slapd-ldap1/ldif2db -n userRoot -E -i /tmp/output.ldif Yeah, I was going to suggest that. Looks like you had some orphan entries in your database. What version of 389-ds-base did you upg

Re: [389-users] dirsrv does not start anymore

2012-03-06 Thread Vasil Mikhalenya
Import of ldif file solved the problem. /usr/lib64/dirsrv/slapd-ldap1/ldif2db -n userRoot -E -i /tmp/output.ldif Now dirsrv works. I think some entries was lost during export from damaged db files. I want dirsrv be more verbose in case of damaged backend db. Verbosity would save much time for us

Re: [389-users] dirsrv does not start anymore

2012-03-06 Thread Vasil Mikhalenya
More info: [root@ldap1 db]# /usr/lib64/dirsrv/slapd-ldap1/db2ldif -n userRoot -E -a /tmp/output.ldif -s "dc=my,dc=domain" -s "o=userRoot" Exported ldif file: /tmp/output.ldif ldiffile: /tmp/output.ldif [06/Mar/2012:18:44:03 +0300] ldif2dbm - _get_and_add_parent_rdns: Failed to position cursor at I