|
Can you please file a ticket:
https://pagure.io/389-ds-base/new_issue And provide the steps to reproduce, although it looks pretty straight forward. Thanks, Mark On 05/02/2017 11:54 AM,
albert.luo@xxxxxxxxxxx wrote:
I have the following problems after upgrading from: 389-Directory/1.3.5.10 B2017.047.2239 to: 389-Directory/1.3.5.10 B2017.093.2133 slapd-ldap12 is one of the directory server instance. 1. a new directory slapd-ldap12.0 under /etc/dirsrv/ drwxrwx---. 4 dirsrv dirsrv 235 May 2 10:46 slapd-ldap12 drwxrwx---. 4 dirsrv dirsrv 220 May 2 10:44 slapd-ldap12.0 2. database backup fail #!/bin/sh #backup db /usr/lib64/dirsrv/slapd-ldap12/db2bak.pl -D "uid=backup_tasks_operator,cn=config " -j some.pwd #export to ldif /usr/lib64/dirsrv/slapd-ldap12/db2ldif -n userRoot error log [02/May/2017:10:44:48.973921266 -0400] Beginning backup of 'ldbm database' [02/May/2017:10:44:48.974718649 -0400] db2archive: mkdir(/var/lib/dirsrv/slapd-ldap12.0/bak/ldap12.0-2017_5_2_10_44_48) failed; errno 2 (No such file or directory) [02/May/2017:10:44:48.975490609 -0400] db2archive failed: removing /var/lib/dirsrv/slapd-ldap12.0/bak/ldap12.0-2017_5_2_10_44_48 [02/May/2017:10:44:48.977120481 -0400] Backup failed (error -1) [02/May/2017:10:44:49.120992823 -0400] chown_dir_files: file (/etc/dirsrv/slapd-ldap12.0/slapd-collations.conf) chown failed (1) Operation not permitted. [02/May/2017:10:44:49.146722858 -0400] chown_dir_files: file (/etc/dirsrv/slapd-ldap12.0/slapd-collations.conf) chown failed (1) Operation not permitted. [02/May/2017:10:44:49.155797890 -0400] db2ldif: can't open /var/lib/dirsrv/slapd-ldap12.0/ldif/ldap12.0-userRoot-2017_05_02_104449.ldif: 2 (No such file or directory) Thank you very much. _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx |
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
