Hello
I am trying out slapo-dds. I haver this in slapd.conf: overlay dds dds-state TRUE dds-max-ttl 1d dds-min-ttl 10s dds-default-ttl 1h dds-interval 120s dds-tolerance 5s
Then I created an entry with this: objectClass: dynamicObject
I had this automatically generated. entryTtl: 3600 entryExpireTimestamp: 20081029215410Z
But now this entry should be expired, and it is still in the tree. What is wrong? Did I misunderstood the documentation, shoudln't it vanish now?
Emmanuel Dreyfus wrote:
Hello
I am trying out slapo-dds. I haver this in slapd.conf: overlay dds dds-state TRUE dds-max-ttl 1d dds-min-ttl 10s dds-default-ttl 1h dds-interval 120s dds-tolerance 5s
Then I created an entry with this: objectClass: dynamicObject
I had this automatically generated. entryTtl: 3600 entryExpireTimestamp: 20081029215410Z
But now this entry should be expired, and it is still in the tree. What is wrong? Did I misunderstood the documentation, shoudln't it vanish now?
Are there any more?
"the lifetime of dynamic objects with subordinates is prolonged until all the dynamic subordinates expire."
Gavin Henry ghenry@OpenLDAP.org wrote:
"the lifetime of dynamic objects with subordinates is prolonged until all the dynamic subordinates expire."
No subordinate: entryTtl: 3600entry ExpireTimestamp: 20081029215410Z hasSubordinates: FALSE
No hint for that problem? If I edit the expired object, entryExpireTimestamp is set to the current time, but the object is still there.
Emmanuel Dreyfus manu@netbsd.org wrote:
Hello
I am trying out slapo-dds. I haver this in slapd.conf: overlay dds dds-state TRUE dds-max-ttl 1d dds-min-ttl 10s dds-default-ttl 1h dds-interval 120s dds-tolerance 5s
Then I created an entry with this: objectClass: dynamicObject
I had this automatically generated. entryTtl: 3600 entryExpireTimestamp: 20081029215410Z
But now this entry should be expired, and it is still in the tree. What is wrong? Did I misunderstood the documentation, shoudln't it vanish now?
Emmanuel Dreyfus wrote:
No hint for that problem? If I edit the expired object, entryExpireTimestamp is set to the current time, but the object is still there.
No clue. I think dds testing is pretty complete, takes care of all cases. Did your build pass test046?
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 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
Pierangelo Masarati ando@sys-net.it wrote:
No clue. I think dds testing is pretty complete, takes care of all cases. Did your build pass test046?
This is on 2.4.11, not HEAD. It works fine on HEAD, I just tested it.
I finally found this; DDS dn="cn=tmp,o=home" err=50; deferring. DDS expired=0
Error 50 suggest I am blocked by an ACL??
Emmanuel Dreyfus wrote:
Pierangelo Masarati ando@sys-net.it wrote:
No clue. I think dds testing is pretty complete, takes care of all cases. Did your build pass test046?
This is on 2.4.11, not HEAD. It works fine on HEAD, I just tested it.
I finally found this; DDS dn="cn=tmp,o=home" err=50; deferring. DDS expired=0
Error 50 suggest I am blocked by an ACL??
Seems it. This message is printed after a delete failure. The only recent change to ACL behavior was for add. I note that deletes are performed by slapo-dds(5) as the rootdn, so unless you don't have a rootdn configured they should always succeed.
This is not mentioned anywhere in slapo-dds(5), so probably it should be documented.
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 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
Pierangelo Masarati ando@sys-net.it wrote:
Seems it. This message is printed after a delete failure. The only recent change to ACL behavior was for add. I note that deletes are performed by slapo-dds(5) as the rootdn, so unless you don't have a rootdn configured they should always succeed.
This is not mentioned anywhere in slapo-dds(5), so probably it should be documented.
Yes, that was the problem.
I opened ITS#5811 and committed a documentation fix.
----- "Emmanuel Dreyfus" manu@netbsd.org wrote:
No hint for that problem? If I edit the expired object, entryExpireTimestamp is set to the current time, but the object is still there.
Nope, but Ando is the best person for this.
openldap-software@openldap.org
-
Gavin Henry -
manu＠netbsd.org -
Pierangelo Masarati