IDM 3.5.1 on eDir 8.8 SP1 FT2, (20114.29), SLES with lots of drivers.

We have a rule in a Loopback driver that when it sees a certain event
(Login Intruder changing from True) it writes back to a Work Order
enough info to close it.

The logic that tests this is working fine. It generates the modify
document, (3 set source attr and 1 add-source-attr) it gets submitted to
eDir with a success returned. All looks good.

I look at the WO objects in C1 or LDAP and the 4 attributes have not
been written to the object.

I have two objects this happened on.

What the heck? I cannot think of where to go with this.

I checked timesync, (4 replicas, all SLES, all in SYnc), Replication
status is as of a few seconds ago. No stuck obits.

No errors in Dstrace with inbound and outbound sync flags on.

I have been looking through the other drivers to see if something else
is going on, but I do not see anything in their traces either.

I am stumped... Why would a write reported as successful in eDir not
show up? (Check, security equals for this driver is to admin)

Now it gets weirder!!! We did the exact same thing a third time, and
the writes happened!! What the heck? (no difference visible in trace
between the two times!)

Any ideas?


Level 3 trace is below:

[01/23/08 12:22:21.284]:Triggered Actions ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.5.2.20070719 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<modify dest-dn="\ACMEIDVAULT\acmeny\APPS\APPLTN\Work
Orders\NOVELL_003-130888" event-id="NYCSUSE2#20080123172220#1#2">
<modify-attr attr-name="DirXML-Other2">
<remove-all-values/>
<add-value>
<value type="string">Intruder Lockout setting has been
cleared</value>
</add-value>
</modify-attr>
<modify-attr attr-name="DirXML-nwoProcessLog">
<add-value>
<value type="string">Intruder Lockout setting has been
cleared</value>
</add-value>
</modify-attr>
<modify-attr attr-name="DirXML-Other1">
<remove-all-values/>
<add-value>
<value type="string">configured</value>
</add-value>
</modify-attr>
<modify-attr attr-name="DirXML-nwoStatus">
<remove-all-values/>
<add-value>
<value type="string">configured</value>
</add-value>
</modify-attr>
</modify>
</input>
</nds>
[01/23/08 12:22:21.305]:Triggered Actions ST: Pumping XDS to eDirectory.
[01/23/08 12:22:21.308]:Triggered Actions ST: Performing operation
modify for \ACMEIDVAULT\acmeny\APPS\APPLTN\Work Orders\NOVELL_003-130888.
[01/23/08 12:22:21.311]:Triggered Actions ST: Modifying entry
\ACMEIDVAULT\acmeny\APPS\APPLTN\Work Orders\NOVELL_003-130888.
[01/23/08 12:22:21.703]:Triggered Actions ST: Processing returned document.
[01/23/08 12:22:21.704]:Triggered Actions ST: Processing operation
<status> for .
[01/23/08 12:22:21.705]:Triggered Actions ST:
DirXML Log Event -------------------
Driver: \ACMEIDVAULT\acmeny\services\ACMEFLAT\Triggered Actions
Channel: Subscriber
Status: Success
[01/23/08 12:22:21.707]:Triggered Actions ST: Direct command from
policy result
[01/23/08 12:22:21.709]:Triggered Actions ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.5.2.20070719 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<status event-id="NYCSUSE2#20080123172220#1#2"
level="success"><application>DirXML</application>
<module>Triggered Actions</module>
<object-dn></object-dn>
<component>Subscriber</component>
</status>
</output>
</nds>
[01/23/08 12:22:21.712]:Triggered Actions ST:Policy returned: