IBM Support

PI42189: SELF UPDATE OF IM THROUGH WEB INTERFACE HANGS SERVER ON MAC AND Z/OS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Installation Manager v 1.8.x on z/OS and Mac fails to restart
    after an self-update initiated from web interface.
    
    If the installed version of IM is not the latest, and "Search
    for Installation Manager updates" option is selected in
    Preferences (File-> Preferences->Updates), then during an
    attempt to perform any install, modify or update of packages, IM
    will show a popup message about availability of a newer version
    of IM-  "A new version of
    Installation Manager is available. ... Do you want to update the
    Installation Manager?" If "Yes" is clicked, IM will fetch
    updates from the online IBM site and apply to itself. This is
    referred to as the "self-update".
    
    After the self-update is complete, the web server is expected to
    restart and web page should refresh after the connection is
    restored to the newly updated IM.
    
    The update initially appears to be successful, and a window pops
    up in the web browser asking for permission to restart the
    server. However, during the restart, the following errors are
    emitted:
    
    1. In the web browser session, a pop-up reports that "The
    Installation Manager's registry information is inconsistent with
    its installation information."  The details report an
    inconsistency between the current version level  (eg. 1.8.1) and
    the update target version level (eg. 1.8.2.1)
    
    2. The following errors occur in the shell session running the
    web interface:
    
    !SESSION 2015-05-13 22:32:15.613
    -----------------------------------------------
    eclipse.buildId=unknown
    
    java.fullversion=JRE 1.7.0 IBM J9 2.6 z/OS s390-31
    20131013_170512 (JIT enabled,
    AOT enabled)
    
    J9VM - R26_Java726_SR6_20131013_1510_B170512
    
    JIT  - r11.b05_20131003_47443
    
    GC   - R26_Java726_SR6_20131013_1510_B170512
    
    J9CL - 20131013_170512
    
    BootLoader constants: OS=zos, ARCH=s390, WS=motif, NL=en_US
    
    Framework arguments:  -toolId ibmim -accessRights group -server
    -eclipse.keyring /InstallationManager/appdata/secure_storage
    
    Command-line arguments:  -os zos -ws motif -arch s390 -toolId
    ibmim -accessRights group -server -consoleLog
    
    
    
    !ENTRY org.eclipse.osgi 4 0 2015-05-13 22:35:57.734
    
    !MESSAGE
    
    !STACK 0
    
    java.io.FileNotFoundException:
    /InstallationManager/bin/eclipse/web/configuration/org.eclipse.o
    sgi/.manager/.fileTableLock (EDC5129I No such file or
    directory.)
            at
    java.io.RandomAccessFile.<init>(RandomAccessFile.java:252)
    
            at
    org.eclipse.core.runtime.internal.adaptor.Locker_JavaNio.lock(Lo
    cker_JavaNio.java:33)
    
            at
    org.eclipse.osgi.storagemanager.StorageManager.lock(StorageManag
    er.java:389)
    
            at
    org.eclipse.osgi.storagemanager.StorageManager.add(StorageManage
    r.java:220)
    
            at
    org.eclipse.osgi.storagemanager.StorageManager.closeOutputStream
    (StorageManager.java:902)
    
            at
    org.eclipse.osgi.storagemanager.ManagedOutputStream.close(Manage
    dOutputStream.java:52)
    
            at
    java.io.FilterOutputStream.close(FilterOutputStream.java:171)
    
            at
    java.io.FilterOutputStream.close(FilterOutputStream.java:171)
    
            at
    org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveBundleData
    s(BaseStorage.java:598)
    
            at
    org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveAllData(Ba
    seStorage.java:461)
    
            at
    org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver.run
    (BaseStorage.java:1306)
    
            at java.lang.Thread.run(Thread.java:804)
    
    
    
    !ENTRY org.eclipse.osgi 4 0 2015-05-13 22:35:58.032
    
    !MESSAGE
    
    !STACK 0
    
    java.io.FileNotFoundException:
    /InstallationManager/bin/eclipse/web/configuration/org.eclipse.o
    sgi/.manager/.fileTableLock (EDC5129I No such file or
    directory.)
            at
    java.io.RandomAccessFile.<init>(RandomAccessFile.java:252)
    
            at
    org.eclipse.core.runtime.internal.adaptor.Locker_JavaNio.lock(Lo
    cker_JavaNio.java:33)
    
            at
    org.eclipse.osgi.storagemanager.StorageManager.lock(StorageManag
    er.java:389)
    
            at
    org.eclipse.osgi.storagemanager.StorageManager.update(StorageMan
    ager.java:291)
    
            at
    org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveStateData(
    BaseStorage.java:670)
    
            at
    org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveAllData(Ba
    seStorage.java:462)
    
            at
    org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver.run
    (BaseStorage.java:1306)
    
            at java.lang.Thread.run(Thread.java:804)
    
    and server appears to hang.
    

Local fix

  • Option A: reinstall IM instead of using self-update
    Option B: manually stop the server after self-update is done
    (press Ctrl-C in the shell where ibmim-web executable was
    launched) and then start the server again
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Installation Manager users attempting to self-update     *
    * their Installation Manager via the web interface on OS X or  *
    * z/OS.                                                        *
    * Self-update:                                                 *
    * If the installed version of IM is not the latest, and        *
    * "Search for Installation Manager updates" option is selected *
    * in Preferences (File-> Preferences->Updates), then during an *
    * attempt to perform any install, modify or update of          *
    * packages, IM will show a popup message about availability of *
    * a newer version of IM-  "A new version of Installation       *
    * Manager is available. ... Do you want to update the          *
    * Installation Manager?" If "Yes" is clicked, IM will fetch    *
    * updates from the online IBM site and apply to itself. This   *
    * is referred to as the "self-update".                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When running the IBM Installation Manager versions 1.8.3 and *
    * earlier on OS X and z/OS platforms using the web interface,  *
    * the Installation Manager fails to restart after a            *
    * self-update.                                                 *
    *                                                              *
    * After the self-update is complete, the web server is         *
    * expected to restart and web page should refresh after the    *
    * connection is restored to the newly updated Installation     *
    * Manager.                                                     *
    *                                                              *
    * The update initially appears to be successful, and a window  *
    * appears asking for permission to restart the server.         *
    * However, during the restart, a pop-up appears in the web     *
    * browser session reporting that "The Installation Manager's   *
    * registry information is inconsistent with its installation   *
    * information."  The details report an inconsistency between   *
    * the current version level  (eg. 1.8.1) and the update target *
    * version level (eg. 1.8.3)                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * A fix for this problem is included in the IBM Installation   *
    * Manager version 1.8.4.                                       *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI42189

  • Reported component name

    IBM INSTALL MGR

  • Reported component ID

    RATLIMG00

  • Reported release

    180

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-01

  • Closed date

    2016-01-20

  • Last modified date

    2016-01-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R160 PSY

       UP

  • R161 PSY

       UP

  • R162 PSY

       UP

  • R163 PSY

       UP

  • R170 PSY

       UP

  • R171 PSY

       UP

  • R172 PSY

       UP

  • R173 PSY

       UP

  • R174 PSY

       UP

  • R180 PSY

       UP

  • R181 PSY

       UP

  • R182 PSY

       UP

  • R183 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDV2W","label":"IBM Installation Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.8","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021