Overview#The Vrdim modules are the NDS modules for DirXML for Linux.
generally, you would not need to know about Vrdim except when Troubleshooting DirXML
Typical location #
/opt/novell/eDirectory/lib64/nds-modules/libvrdim.* -rwxr-xr-x 1 root bin 1309 Jun 1 2012 libvrdim.la lrwxrwxrwx 1 root bin 17 Jul 16 13:31 libvrdim.so -> libvrdim.so.3.0.0 lrwxrwxrwx 1 root bin 17 Jul 16 13:31 libvrdim.so.3 -> libvrdim.so.3.0.0 -rwxr-xr-x 1 root bin 343787 Jun 1 2012 libvrdim.so.3.0.0
Loading and unloading#Normally, the modules will load anytime the binaries are installed.
If required, you can manually unload and load vrdim.
Possible Help Links#
- Identity Manager 4.0.x Engine fails to load after the installation of eDirectory 8.8 SP8 Patch 4
- New IDM install fails to start on OES11 (shipping) or Redhat 6.2 -783 VRDIM Not Initialized
- Troubleshooting -641 or -783 Errors Starting an IDM driver - eDirectory fails to load (vrdim)
- -783 Unable to load VRDIM at driver startup. -299 error in NDS Trace
DirXML 188.8.131.52 SE Multiple eDirectory instances are installed. After we add a new server to the driverSet. When we try to start a driver on the server we obtain the following dialog:
Unable to start the driver IDV to Unix.DriverSet.esc.willeke.com com.novell.admin.common.exceptions.UniqueSPIException: (Error -783) The DirXML Interface Module [VIRDIM] is not currently loaded into NetWare or into DHost.
Also, when we perform:
ndstrace -c modules --config-file /data/nds/idv/nds.conf|grep 'vrdim' Not Loaded vrdimThe vrdim module must be loaded for IDM to work. Re-booting the server does not fix the issue.
Although manually loading the module, appeared to load,
ndstrace -c "load vridm' --config-file /data/nds/idv/nds.confwe still get the (Error-783)
Prevent DirXML from autoloading when eDirectory (NDSD) starts#
Then move the libraries back and restart ndsd or use:
ndstrace -c "load vridm' --config-file /data/nds/idv/nds.conffrom within ndstrace.
In this case#As it turned out, the issue was with the EDirectory 184.108.40.206 upgrade that changed the DirXML Engine JVM We also would see these entries within the trace logs:
2013091584 MISC: [2014/07/29 15:52:52.7] Entry .DriverSet.esc.willeke.com. has an Illegal Attr Name: .sssActiveServerList.[Attribute Definitions].[Schema Root], failed, illegal attribute (-608)
The key was finding this error in the trace files:
The Identity Manager 4.0.x engine fails to load and the following error messages are shown in ndstrace +dxml: DirXML starting. Error initializing DirXML: java.lang.UnsupportedClassVersionError: novell/jclient/JCContext at com.novell.nds.dirxml.engine.MiscDS.createLocalContext(MiscDS.java:73) at com.novell.nds.dirxml.engine.DirXML.run(DirXML.java:255) at java.lang.Thread.run(Unknown Source) DirXML shutting down... DirXML shutting down.
More Information#There might be more information for this subject on one of the following:
- DirXML Engine JVM
- IDM Start-Stop
- IDM Tricks
- NDSD Loadable Module
- NDSTRACE Examples
- Troubleshooting DirXML
- [#1] - To prevent DirXML from autoloading when NDSD starts - based on information obtained 2018-08-18-
- [#1] - Identity Manager Driver Errors - based on information obtained 2018-08-18-