IBM Support

PK62242: INCORRECT ERROR HANDLING IN IBM HTTP SERVER WHEN SIDD IS NOT FOUND UNDER SERVER ROOT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • INCORRECT ERROR HANDLING IN IBM HTTP SERVER WHEN SIDD IS NOT
    FOUND UNDER SERVER ROOT.
    WHEN TRYING TO START IBM HTTP SERVER
    WITHOUT SETTING SSLCACHEPATH TO FULL PATH TO SIDD, ERROR.LOG
    MAY SHOW:
    (2)No such file or directory:
    SSL0600S: Unable to connect to session ID cache
    

Local fix

  • WORKAROUND: SET FULL PATH TO SID USING SSLCACHEPATH DIRECTIVE IN
    HTTPD.CONF.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: mod_ibm_ssl configurations on platforms      *
    * other than Windows with non-default ServerRoot               *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the sidd executable file is not      *
    * found under the server root in file bin/sidd, a helpful      *
    * error message is not written and IBM HTTP Server may retry   *
    * to start sidd every two seconds.  Session ID caching will    *
    * not be operational and performance will be degraded.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the ServerRoot directive is modified to point outside of the
    IBM HTTP Server install directory, the SSLCachePath directive
    must be used to point to the sidd executable file within the
    product install directory.
    If SSLCachePath is not specified, mod_ibm_ssl will not be able
    to start sidd and SSL session IDs will not be cached.
    Depending on the maintenance level, no message will be issued
    for this error or a generic SSL0601E message will be
    issued.  If SSL0601E is issued, the exit code logged, 255, is
    not documented.
    

Problem conclusion

  • A check for the sidd executable file is now made prior to
    creating the new child process so that this error can be
    handled synchronously before initialization proceeds; a more
    helpful message is now displayed.  Example:
    .
     crit  (2)No such file or directory: SSL0604E: Unable to start
    session ID cache program /usr/IBMIHS/bin/sidd
    .
    If the permissions of the bin/sidd file are incorrect, the
    same message will be issued but with a different error number
    and string.
    .
    This fix is targeted for fix packs
      6.1.0.17
      6.0.2.29
    and cumulative fix PK65782 for IBM HTTP Server 2.0.47
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK62242

  • Reported component name

    IBM HTTP SERVER

  • Reported component ID

    5724J0801

  • Reported release

    60S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-03-05

  • Closed date

    2008-03-19

  • Last modified date

    2008-05-23

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

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

Fix information

  • Fixed component name

    IBM HTTP SERVER

  • Fixed component ID

    5724J0801

Applicable component levels

  • R60A PSN

       UP

  • R60H PSN

       UP

  • R60I PSN

       UP

  • R60P PSN

       UP

  • R60S PSN

       UP

  • R60Z PSN

       UP

  • R61A PSN

       UP

  • R61H PSN

       UP

  • R61I PSN

       UP

  • R61P PSN

       UP

  • R61S PSN

       UP

  • R61Z PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTJ","label":"IBM HTTP Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0"}]

Document Information

Modified date:
23 October 2021