OES 24.3 and iManager update problems

After upgrading our three OES servers to OES 24.3 I noticed, that a smooth upgrade of  iManager plugins is impossible.

There were 4 new npms:

   base 3.2.6.20240514

   fw 3.2.6.20240514

   iman_sp 3.2.6.20240514  and

   iPrintX 2.7.7.20240526 .

Trying to install them by selecting all and hitting "Installation" crashed on all 3 servers. This because the uninstallation of the previous version cashed with errors like:

novell-tomcat[1477]: iPrint-iManager (Linux plugin): Init
novell-tomcat[1477]: iPrint-iManager (Linux plugin): setData: /var/opt/novell/iManager/nps/packages/iPrint_Linux_iMan27.npm
novell-tomcat[1477]: iPrint-iManager (Linux plugin): Init
novell-tomcat[1477]: iPrint-iManager (Linux plugin): setData: /var/opt/novell/iManager/nps/packages/iPrint_Linux_iMan27.npm
novell-tomcat[1477]: Entering uninstall FwZipOps: npmPath: /var/opt/novell/iManager/nps/packages/iPrint_Linux_iMan27.npm webAppRoot: /var/opt/novell/iManager/nps
novell-tomcat[1477]: java.home is/usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre
novell-tomcat[1477]: os.name isLinux
novell-tomcat[1477]: launchExec command: /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre/bin/java -Djava.awt.headless=true -jar /var/opt/novell/iManager/nps/UninstallerData/Uninstall_iPrintX/uninstaller.jar -i silent
novell-tomcat[1477]: =======================================================
novell-tomcat[1477]: Unable to launch installer.
novell-tomcat[1477]: The installer found unexpected changes to the install script.
novell-tomcat[1477]: =======================================================
novell-tomcat[1477]: Error installing NPM. Return code = 208
novell-tomcat[1477]: FwZipOps: Warning: Uninstall of the plug-in /var/opt/novell/iManager/nps/packages/iPrint_Linux_iMan27.npm - failed.
novell-tomcat[1477]: Exiting uninstall FwZipOps with no exceptions: npmPath: /var/opt/novell/iManager/nps/packages/iPrint_Linux_iMan27.npm webAppRoot: /var/opt/novell/iManager/nps
novell-tomcat[1477]: Exception in thread "fw.ModulesToInstall" java.lang.IllegalStateException: The request object has been recycled and is no longer associated with this facade
novell-tomcat[1477]: #011at org.apache.catalina.connector.RequestFacade.checkFacade(RequestFacade.java:856)
novell-tomcat[1477]: #011at org.apache.catalina.connector.RequestFacade.getHeader(RequestFacade.java:516)
novell-tomcat[1477]: #011at javax.servlet.http.HttpServletRequestWrapper.getHeader(HttpServletRequestWrapper.java:82)
novell-tomcat[1477]: #011at com.novell.emframe.fw.filter.RequestWrapper.getHeader(RequestWrapper.java:303)
novell-tomcat[1477]: #011at javax.servlet.http.HttpServletRequestWrapper.getHeader(HttpServletRequestWrapper.java:82)
novell-tomcat[1477]: #011at com.novell.emframe.fw.DownloadAndInstallWorker.process(DownloadAndInstallWorker.java:198)
novell-tomcat[1477]: #011at com.novell.emframe.dev.BasicCollectionAsyncWorker.run(BasicCollectionAsyncWorker.java:70)
novell-tomcat[1477]: #011at com.novell.emframe.fw.FwAsyncContext$FwAsyncThread.run(FwAsyncContext.java:182)

On one server I could overcome this by installing each npm by itself and restarting novell-tomcat after each failure (approximately 8 restarts). On one server one plugin could not be installed by that method, so I had to resort to uninstalling the plugin manually by deleting all installed files and folders and afterwards I could install the plugin normally (because it did not try to uninstall it in the first instance) and on the third server (the one, which had been installed originally as OES 2023) installation failed completely.

Although those upgrades are probably not essential, the complications you get with this behaviour are quite annoying.

Initially I was very pleased with the upgrade to 24.3, because the upgrade process itself went smooth on all servers and all services were up after the upgrade without resorting to special tweaks.

Reagards

Tags:

  • 0  

    Note that iManager has been deprecated by the eDir team, with eDir specific bits being handled by their new Identity Console. Since they dropped that change in direction, the OES team has been busy building UMC to be the replacement for all the OES stuff that was in iManager that isn't core eDir. The next version of OES is supposed to have Identity Console more readily available than its current manual installation from the eDir side of things.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   

    I know, but unfortunately not all OES things, which are manageable via iManager, can already be managed by UMC/Idendity Manager .

  • 0   in reply to 

    So far, with just one iManager updated, I haven't had a problem installing them all at once.

      However I did get a number of Return code =208
         but it just chugged through despite that.

    a restart of novell-tomcat,  and all looks good so far.  I suspect there is some other factor involved.
     - Perhaps that we have more npms involved. this box has NCS and LUM
     - and/or history of box, this was upgraded from OES 2018.3, that was new as 2018.0

    As for not all OES things on the new stuff yet, this is your chance to articulate what you are finding missing. Either someone here can tell you where it is hiding now, get an ETA on when it should be there, or get an Idea to rattle the cages about.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • Suggested Answer

    0  

    I faced same problem as you and found, that solution is to deploy dockerized iManager, There is no problem with plugins install or update. So far everything is working as indented.

    David