Highlighted
jwilleke Trusted Contributor.
Trusted Contributor.
117 views

Move from XDAS to CEF

Seems like this should be simple and that someone else would have documented the process. (Like the vendor).

ndstrace -c "load cefauditds"
Jul 16 10:56:35 NetIQ eDirectory CEF Instrumentation cannot be loaded as XDAS audit system is already loaded!

ndstrace -c "unload xdas"
Jul 16 10:57:44 NetIQ eDirectory XDASv2 Instrumentation module stopped

ndstrace -c "load cefauditds"
Jul 16 10:57:57 NetIQ eDirectory CEF Instrumentation cannot be loaded as log4cxx is already in use with a different module.

So I assume the xdas has loaded the module and will not release it.
To stop XDAS from loading we need to disable auto-loading:
vim /etc/opt/novell/eDirectory/conf/ndsmodules.conf

# xdasauditds auto #xdasauditds

and restart instance.

No joy. restarting still get  NetIQ eDirectory CEF Instrumentation cannot be loaded as log4cxx is already in use with a different module even though xdasauditds Not Loaded.

Any ideas? Thanks

-jim

Labels (1)
0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Re: Move from XDAS to CEF

Hi Jim,

does this server also runs an IDM engine?

Can you manually load cefauditds after the eDirectory restart?

If so, please open an SR referring to Bug 1139251 - Unable to load cefauditds. It seems to be a race condition between IDM and eDirectory initializing log4cxx.

 

Norbert

0 Likes
jwilleke Trusted Contributor.
Trusted Contributor.

Re: Move from XDAS to CEF

does this server also runs an IDM engine?
Yes

Can you manually load cefauditds after the eDirectory restart?
No

After trying several different items we determined that the entry within the nds.conf file appeared to be causing the issue.

We had:
n4u.server.xdas-conf=/.../nds/instances/xdasconfig.properties
n4u.server.audit-conf=/.../nds/instances/auditlogconfig.properties

Removing the "xdasconfig.properties" entry allowed the module to load.

We do have repeating entries in ndsd.log similar to:

Jul 17 00:40:03 log4cxx: Connection to TCP host established successfully: infra-logging....
Jul 17 00:50:03 log4cxx: Detected problem with TCP connection to infra-logging..... All logging will FAIL.
Jul 17 00:50:03 log4cxx: IO Exception : status code = 104
Jul 17 01:00:03 log4cxx: Connection to TCP host established successfully: infra-logging....
Jul 17 01:10:03 log4cxx: Detected problem with TCP connection to infra-logging..... All logging will FAIL.
Jul 17 01:10:03 log4cxx: IO Exception : status code = 104
Jul 17 01:20:03 log4cxx: Connection to TCP host established successfully: infra-logging....
Jul 17 01:30:03 log4cxx: Detected problem with TCP connection to infra-logging..... All logging will FAIL.
Jul 17 01:30:03 log4cxx: IO Exception : status code = 104

These repat at these same what appear to be 1 hour intervals every since the module loaded.
10 Minutes after we see:
Connection to TCP host established successfully

Then:
Detected problem with TCP

BY WAY:
eDirectory 9.1.2 IDM 4.7.1

 

-jim

 

 

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Move from XDAS to CEF

104 = Connection reset by peer

So its either a firewall in between or the logserver itself closing the connection after some time.

jwilleke Trusted Contributor.
Trusted Contributor.

Re: Move from XDAS to CEF

Thanks. We will contact the Firewall team as they are famous for DROPPING connections without closing the TCP connection. And as we were on UDP with XDAS that makes sense.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.