PI90811: rotatelogs fails with relative paths in IBM HTTP Server V9

9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Full path to rotatelogs is required in the httpd.conf for IBM
  HTTP Server V9
  

Local fix

• Code the full path to rotatelogs in the httpd.conf.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IHS v9 with rotatelogs             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Relative paths are not working for      *
  *                      rotatelogs in IHS v9                    *
  ****************************************************************
  * RECOMMENDATION:  Apply this fix if using IHS v9 with         *
  *                  rotatelogs                                  *
  ****************************************************************
  With IHS 8.5, the full path to rotatelogs was not required in
  the httpd.conf as long as the path to the script was in the
  PATH envvar.  As of v9, attempting to use the relative path in
  the httpd.conf will result in an error in the error log like
  the following:
  EDC5129I No such file or directory.
  (errno2=0x053B006C): AH00088: exec of 'rotatelogs' failed
  (129)EDC5129I No such file or directory. (errno2=0x0516006C):
  AH00104: unable to start piped log program
  'rotatelogs -l logs/access_log.%Y.%m.%d 5M'
  

Problem conclusion

• If a piped logger is given with a relative path, check under
  the ServerRoot
  and ServerRoot's bin/ subdirectory for a match instead of
  failing.
  
  This fix is targeted for IBM HTTP Server fix packs:
  - 9.0.0.7
  

Temporary fix

• Code the full path to rotatelogs in the httpd.conf.
  

Comments

APAR Information

• 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

  WAS IHS ZOS

• Fixed component ID

  5655I3510

Applicable component levels

• R90P PSY

     UP