Error saving driver persistent data
IDM 4.7.3 on SLES 12.
In ndstrace with +dvrs I see this error, any tips on what to do?
3063748352 DVRS: ENG ET:
DirXML Log Event -------------------
Message: Code(-9203) Error saving driver persistent data: Code(-9010) An exception occurred: com.novell.nds.io.JCIOException: openStream: -166
Caused by: novell.jclient.JCException: openStream -166 DSERR_ALREADY_IN_USE
at novell.jclient.JClient.openStream(Native Method)
... 10 more
It looks like a relatively old and known issue with driver persistent data "corruption".
It described in the next TID
Delete the attribute DirXML-PersistentData from the problem driver. This can be done via LDAP or ConsoleOne, iManager 2.7.3 does not provide access to the attribute. After that the driver should start normally.
DirXML-PersistentData stores counters for health monitoring. If the attribute XML content get corrupted, the errors mentioned in this TID will occur.
Since it is is recreated when it does not exist and the driver is started, there is no loss of driver configuration or logic in deleting the DirXML-PersistentData attribute.
Also I am pretty sure that DirXML-PersistentData is per replica, which is why it is hard to delete with iManager. So make sure to clear it on any replicas that the driver could run on.
Side note: Alekz - any chance when working with a Per-Replica attribute in Console2 do you think you could provide a UI to show all possible values on different replica? That would be super duper handy!
Is this in relation to RRSD driver by any chance? I ask because I have seen this on a box that pretty much just runs RRSD and IDM Apps.
Specifically, since they added parallel processing support to RRSD, the driver uses the DirXML-DriverStorage attribute (a per replica attribute) to keep track of things. This is documented here https://www.netiq.com/documentation/identity-manager-48/identity_apps_admin/data/multi-thread-rrs-troubleshooting.html
When all is well, the attribute is updated once the processing is completed.
What I suspect is we are seeing some sort of conflict or locking failure in updating this attribute.
Running RRSD 184.108.40.206 + IDM 220.127.116.11 AE + eDir 9.1.4 on windows where I see this issue.
Interested if anyone else can report as to what versions they run.