On 08/02/2013 01:51 AM, Carsten Grzemba wrote:
Hi Rich,
Am 01.08.13 schrieb *Rich Megginson * :
On 08/01/2013 02:35 PM, Tim Daley wrote:
Just tried it. Looks like I'm still getting 389-ds-base.x86_64
0:1.2.11.21-1.el6_4 when I do a
yum clean all
yum --enablerepo=epel-testing-389-ds-base --en
Hey,
Certainly new to migrations of LDAP. I migrated our old setup from OpenLDAP
to 389 Directory Server. When using the "id" command on an LDAP client, it
only returns uid,gid, and one group. It for some reason does not show all
of the actual groups that the user is associated with. What is set to
On 08/02/2013 01:30 AM, Manel Gimeno Zaragozá wrote:
Hello,
Yesterday afternoon my LDAP server crashed without doing any
modification, just consulting.
My environment is an openvz container:
# cat /etc/issue
CentOS release 6.4 (Final)
Kernel \r on an \m
# uname -a
Linux newldap.test.es 2.6.
Hi Rich,
Am 01.08.13 schrieb Rich Megginson :
>
>
>
>
>
> On 08/01/2013 02:35 PM, Tim Daley wrote:
>
>
> > Just tried it. Looks like I'm still getting 389-ds-base.x86_64
> > 0:1.2.11.21-1.el6_4 when I do a yum clean all
> > yum --enablerepo=epel-testing-389-ds-base --enablerepo=epe
If the database panics, it has detected a state of inconsistency it
cannot resolve and sets a panic flag to the database environment to
prevents its use. Just restarting the ds will detect the flag and abort.
You can try to remove the __db.00* files and then start DS again, if
this fails you nee
Hello,
Yesterday afternoon my LDAP server crashed without doing any modification, just
consulting.
My environment is an openvz container:
# cat /etc/issue
CentOS release 6.4 (Final)
Kernel \r on an \m
# uname -a
Linux newldap.test.es 2.6.32-042stab053.5 #1 SMP Tue Mar 27 11:42:17 MSD 2012
x86
