After RHEL8 upgrade, Peoplesoft driver doesn't attempt to connect to remote loader

We are preparing for an eDir and IDM version upgrade, from 9.2.6 and 4.8.3 to 9.2.9 and 4.8.7. We currently run on RHEL 7, but RHEL 8 is the minimum OS for the latest eDir installer, so we've done in-place OS upgrades on our servers from RHEL 7 to RHEL 8 without any noticeable issues except that the Peoplesoft driver and LDAP driver we have no longer attempt to send connections off the IDM server to the remote loader or target OpenLDAP server, verified with tcpdump.

To further complicate matters, other JDBC drivers on the same IDM server will connect to the remote loader server just fine. And all our other drivers that make connections off the IDM server (Google, AD, etc) all work fine as well.  We can also, using netcat, make the expected connections from the IDM server to the remote loader server or the OpenLDAP server, and from the remote loader to the Peoplesoft IB servers, so it's not like a firewall issue or something.

We have an SR open but I figured I'd ask the hive mind for thoughts or suggestions on where to look or why the packet sends are never attempted for these particular driver types.

  • 0  

    There have been at least 3 different cases where the wrong RPM Is in use causing issues.

    1) XDAS - there is a version 6 and 14, and you need the v14 installed.  For 9.28. and 9.29 something like this (I grabbed off a 9.2.7 system and modified by hand)

    novell-edirectory-xdaslog-9.2.8.0000-14_x86_64

    2) CEF: Same sort of issue, you need the version from IDM not eDir of cefauditds fails to load.

    novell-edirectory-cefinstrument-9.2.8.0000-252.x86_64

    3) I forgot the specific details but there is a jclient.jar I think from iManager that causes issues if the install order is wrong.  (iMan before or after eDir I think before) that causes load issues.

    There is one for email issues but I forget the details.

    My first thought would be to try those three packages/jars to see if it has any bleed over into your problem area.

  • 0   in reply to   

    I should mention that often the missing RPM is in the IDM install directory on the DVD.  As opposed to eDir.  There are a whole set (Linux version of course) that might be worth double checking are in use.  (We ran into this with an eDir->IDM->eDir install process).

  • 0 in reply to   

    Thanks, we have not yet upgraded eDir or IDM. This outcome was only after a RHEL7->RHEL8 upgrade on the server.

  • 0   in reply to 

    The eDir/IDM compat issue between RHEL7->8 seems to be that the locations of the libstdc++ changed on the RHEL side.

    So you need a different set of symlinks.  Which is in the Readme notes how to fix/not fix.  I.e.  Breaks earlier versions, new version knows to use the proper symlinks or somesuch. 

  • 0

    Update - problem solved (although I'm not sure 100% why, and we're still asking for help from OpenText).  The drivers which wouldn't start have policies that (used to) send mail to ServiceNow and create tickets for certain types of data problems.  With the upgrade to RHEL 8, postfix needed a "compatibility_level = 2" added to main.cf and then get restarted. There were a few SELinux cleanups that needed to be made as a result, but once postfix was happy, the drivers started right up.

    We were so focused on the idm->remote loader connection that we didn't point tcpdump at idm->localhost connections, and certainly didn't think mail might be a root cause.