On 05/02/2017 02:56 PM, albert.luo@xxxxxxxxxxx wrote: > Hi, Mark, > > I couldn't reproduce the problem. The other two servers upgraded didn't have this problem. There are two instance of slapd on this server. Only one instance have this problem. > > /etc/sysconfig/dirsrv-ldap12.0 > diff /etc/sysconfig/dirsrv-ldap12.0 /etc/sysconfig/dirsrv-ldap12 > 15c15 > < CONFIG_DIR=/etc/dirsrv/slapd-ldap12.0 > --- >> CONFIG_DIR=/etc/dirsrv/slapd-ldap12 > /usr/lib64/dirsrv/slapd-ldap12 > # grep ldap12.0 * |more > bak2db:/usr/sbin/bak2db "$@" -Z ldap12.0 > bak2db.pl:exec "/usr/sbin/bak2db.pl @wrapperArgs -Z ldap12.0"; > cleanallruv.pl:exec "/usr/sbin/cleanallruv.pl @wrapperArgs -Z ldap12.0" > db2bak:/usr/sbin/db2bak "$@" -Z ldap12.0 > db2index:/usr/sbin/db2index "$@" -Z ldap12.0 > > Changing "ldap12.0" to "ldap12" in the bak2db.pl script fixed the backup failure. Odd, I am not familiar with these ".0" files being created. Anyway the source is on pagure: git clone https://pagure.io/389-ds-base.git cd 389-ds-base git checkout 389-ds-base-1.3.5 cd ldap/admin/src/scripts The perl modules are used to do the upgrade/setup stuff: DSUtil.pm DSCreate.pm DSUpdate.pm Regards, Mark > > I am trying to understand how these "ldap12.0" files were created during the upgrade, If possible manually change these files to fix the problem. > > Could you please point me the detail log of the upgrade process and the source code that create these files? 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
