Is there a known memory leak?
by Gioachino Bartolotta
Hi all,
I have a problem with the 389-ds
I setup the machine (CentOS 5.6 amd64) with 4 GB RAM and 4 GB Swap, 2
cores and installed
389-ds-console-1.2.5-1.el5
389-ds-base-libs-1.2.8.3-1.el5
389-ds-base-1.2.8.3-1.el5
389-dsgw-1.1.6-1.el5
389-ds-1.2.1-1.el5
389-ds-console-doc-1.2.5-1.el5
Set up also samba from sernet repos (samba 3.4)
Anyway is consuming a lot of memory even if there is no one using it
.... (this picture has been taken yesterday with no one in office)
Is there something I have to see to reduce the memory usage, or it's a
known bug?
Actually I restart the dirsrv when it consumes all the ram available.
Thanks
--
-------------------------------------------
Gioachino Bartolotta
ICQ #: 9103167
MSN Messenger: astraroth(a)email.it
Yahoo & Skype: gioachino_bartolotta
12 years, 9 months
admin password expired ??
by Gioachino Bartolotta
Hi all,
I set up the password policies on the 389 directory server, and now it
happens that when I try to log in as admin, it says "Password
expired".
How it's possible? The admin user is the one setup for management with
the 389 console ....
Please help!
--
-------------------------------------------
Gioachino Bartolotta
ICQ #: 9103167
MSN Messenger: astraroth(a)email.it
Yahoo & Skype: gioachino_bartolotta
12 years, 9 months
389-ds apparently listens only on loopback
by Arian Sanusi
Hi all,
I set up a host with centos 5.6 and 389-ds 1.1.3 for testing purposes.
On startup of the directory, it states:
[08/Jul/2011:15:36:44 +0200] - 389-Directory/1.2.2 B2009.237.2054
starting up
[08/Jul/2011:15:36:46 +0200] - slapd started. Listening on All
Interfaces port 389 for LDAP requests
[08/Jul/2011:15:36:47 +0200] - Listening on All Interfaces port 636 for
LDAPS requests
on that host I can see ldap and ldapssl ports open, and p.ex.
389-console shows reasonable stuff.
However, on other hosts I cannot, queries on the directory fail - Seems
to me like the server only listens on the loopback interface.
Any Ideas about this?
regards, Arian
12 years, 9 months
changing passwords
by Kyller Costa Gorgônio
Hi,
I have setup my 389 directory server (in fact it's a centos-ds) and
now I need to allow my users to change their passwordss. The problem
is that most of my users do not have a shell script and/or I do not
trust their clients.
I need to provide some web page so that thay can do it. Does anyone
has any sugestion?
cheers
--kyller
12 years, 9 months
Converting a consumer into a multi-master?
by Penedo
Hello,
Our setup has one location with a pair of multi-masters (call it "location
A") and another location with a pair of consumers (call it "location B".
I'd like to "switch directions" between the locations so the servers in
"location B" will be multi-masters between themselves and the servers in
location "A" will be "downgraded" to simple consumers.
As far as I understand the documentation, this might be possible by adding
the "missing replication agreements (i.e. tell the "location B" servers to
become multi-masters and tell the current multi-masters in "location A" to
also accept updates from "location B").
Effectively, this should convert the current two-way multi-master cluster in
"location A" into a four-way multi-master cluster across "location A" and
"location B". Once this is done I expect that I can "downgrade" the
"location A" servers to simple consumers by removing the current replication
agreement they have (or even replace them with a new installation altogether
if that's not possible).
Am I correct or is it more complicated than that?
Thanks,
-P
12 years, 9 months
389-DSGW and userPassword / sambaNTPassword / sambaLMPassword synchronization
by Alexandr Popov
Hello!
I've got a directory server and DSGW running.
Mail server, openvpn server and samba share use ldap authentication against
this directory server. Users change their passwords in DSGW.
The mailserver and openvpn use SSHA hash in "userpassword" field, but samba
uses NT hash and LM hash in "sambantpassword" and "sambalmpassword" fields
accordingly.
How can I make "userpassword" , "sambantpassword" and "sambalmpassword"
fields change synchronously when users change their passwords in DSGW?
As I can understand, there is no already written 389-DS-plugin for
synchronizing
these fields.
Moreover, it seems to me that such issues as mine are often solved on the
ldap clients:
http://web.archiveorange.com/archive/v/I3m7YImbRJ3Dj9WoXlCz
Am I right?
So should I change
domodify.c<http://git.fedorahosted.org/git?p=389/dsgw.git;a=blob;f=domodify.c;h=5a37...>which
is responsible for password change in DSGW? Does it seem to be useful
for Community?
Looking forward to your prompt repy.
Best regards,
Alex Popov.
12 years, 9 months