Hi,
I am having a problem with changing password against consumer server. However, the problem would be gone if the loglevel is set to "1" or "-1" on the consumer server. If loglevel is set to other value, slapd would crash upon last communication during password changing process. Such problem does not appear on provider, on which I can set loglevel to any value without issue. Consumer server has chain overlay setup.
Here are the commands I used for testing:
ldappasswd -v -H ldap://provider -D "uid=user1,ou=people,dc=example,dc=com" -W -S -x -A (Works all the time) ldappasswd -v -H ldap://consumer -D "uid=user1,ou=people,dc=example,dc=com" -W -S -x -A (Works only when loglevel set to 1 or -1)
The servers run 2.3.35 with bdb-4.5.20_p2. Client runs 2.3.27. Could this be related to chain overlay setup? or something else? What's so confusing is that it worked under certain situations, but not others.
Simon
Simon Gao wrote:
Hi,
I am having a problem with changing password against consumer server. However, the problem would be gone if the loglevel is set to "1" or "-1" on the consumer server. If loglevel is set to other value, slapd would crash upon last communication during password changing process. Such problem does not appear on provider, on which I can set loglevel to any value without issue.
Please file an its along the lines of http://www.openldap.org/faq/data/cache/59.html.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
Pierangelo Masarati wrote:
Simon Gao wrote:
Hi,
I am having a problem with changing password against consumer server. However, the problem would be gone if the loglevel is set to "1" or "-1" on the consumer server. If loglevel is set to other value, slapd would crash upon last communication during password changing process. Such problem does not appear on provider, on which I can set loglevel to any value without issue.
Please file an its along the lines of http://www.openldap.org/faq/data/cache/59.html.
Where do I file an ITS?
I found if I run slapd manually as front process, then I can set "-d" to any value without seeing the problem. Loglevel in slapd.conf is the same as "-d" when running slapd at command line, correct? If so, then the problem seems to be related to writing to syslog file in particular.
Simon
--Quanah
--On June 18, 2007 3:09:59 PM -0700 Simon Gao gao@schrodinger.com wrote:
Pierangelo Masarati wrote:
Simon Gao wrote:
Hi,
I am having a problem with changing password against consumer server. However, the problem would be gone if the loglevel is set to "1" or "-1" on the consumer server. If loglevel is set to other value, slapd would crash upon last communication during password changing process. Such problem does not appear on provider, on which I can set loglevel to any value without issue.
Please file an its along the lines of http://www.openldap.org/faq/data/cache/59.html.
Where do I file an ITS?
I found if I run slapd manually as front process, then I can set "-d" to any value without seeing the problem. Loglevel in slapd.conf is the same as "-d" when running slapd at command line, correct? If so, then the problem seems to be related to writing to syslog file in particular.
Simon
-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org
-
Pierangelo Masarati -
Quanah Gibson-Mount -
Simon Gao