IBM Support

PK68392: INVALID DIRECTORY PATH SET IN ROTATELOGS CAUSE ERRORS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a invalid directory (non existing) is set in the Customlog
    location for rotatelogs.exe, it cause the below errors.
    
    -----
      ErrorLog rotatelogs set
    .
    ErrorLog "|bin/rotatelogs.exe logs/error_pmr27430_%Y%m%d.log
    86400 600"
    .
      CustomLog rotatelogs set + c:/test/IHS/logs/ folder does not
    exist. (
    c:/test/IHS/logs/ folder deleted. )
    .
    CustomLog "|bin/rotatelogs.exe logs/access_pmr27430_%Y%m%d.log
    86400 60
    0" common
    CustomLog "|bin/rotatelogs.exe
    c:/test/IHS/logs/access_test_fol_pmr2743
    0_%Y%m%d.log 86400 600" common
    -----
    

Local fix

  • Not set an invalid path to the Customlog directory for
    rotatelogs.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM HTTP Server configurations with          *
    * piped loggers such as rotatelogs                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a piped logger such as rotatelogs    *
    * fails, IHS on Windows is unable to restart the piped logger. *
    ****************************************************************
    * RECOMMENDATION: This fix is recommended for Windows systems  *
    * with configurations with references to rotatelogs or other   *
    * piped loggers.                                               *
    ****************************************************************
    Rotatelogs will fail if, for example, an invalid path is
    supplied in the CustomLog or TransferLog directive.  On Windows,
    the piped logger will not be restarted properly and a web server
    hang may occur after a large number of requests.
    IHS tries to restart the piped logger but does so with an
    invalid handle on Windows.  This error does not occur on other
    platform but a handle is leaked.
    

Problem conclusion

  • IHS on Windows was changed to pass a valid handle to the
    replacement piped logger (e.g. rotatelogs).  On other platforms
    handles are properly closed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK68392

  • Reported component name

    IBM HTTP SERVER

  • Reported component ID

    5724J0801

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-07-01

  • Closed date

    2008-07-02

  • Last modified date

    2008-07-02

  • 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

  • R60P PSN

       UP

  • R60I PSN

       UP

  • R60S PSN

       UP

  • R60W PSN

       UP

  • R60Z PSN

       UP

  • R61A PSN

       UP

  • R61H PSN

       UP

  • R61P PSN

       UP

  • R61I PSN

       UP

  • R61S PSN

       UP

  • R61W PSN

       UP

  • R61Z PSN

       UP

[{"Line of Business":[],"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTJ","label":"IBM HTTP Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1"}]

Document Information

Modified date:
25 September 2020