We tried to load the a2 389-ds-base and we were unable to start the server. I will go back and try to pull the logs for you but it was 3AM and I am not sure I saved them.
gc "Motorcycling is not, of itself, inherently dangerous. It is, however, extremely unforgiving of inattention, ignorance, incompetence, or stupidity." author unknown
On Feb 25, 2011, at 6:18 AM, Rich Megginson wrote:
On 02/25/2011 12:13 AM, Gordon Cooke wrote:
I ran a yum update on one of my 2 LDAP server last
night and am encountering this issue:
yum installed as follows:
[root@blair slapd-blair]# rpm -qa |grep 389
389-adminutil-1.1.13-1.el5
389-ds-console-1.2.3-1.el5
389-dsgw-1.1.6-1.el5
389-admin-console-doc-1.1.5-1.el5
389-admin-1.1.14-1.el5
389-admin-console-1.1.5-1.el5
389-console-1.1.4-1.el5
389-ds-base-1.2.7.5-1.el5
389-ds-console-doc-1.2.3-1.el5
389-ds-1.2.1-1.el5
I am wondering if there is a known workaround for this short
of recompiling with the changes identified in the patch. This
is on RHEL5.6
The fix is now available in epel testing - try
yum update --enablerepo=epel-testing 389-ds-base
Thanks for your help!!
Gordon
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
|
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
