PH03059: ABENDEC6 RC FF0F SEEN AT SERVER STARTUP USING ROTATELOGS

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

APAR status

• Closed as program error.

Error description

• At startup, Apache does a dry run of startup before fully
  daemonizing. This includes starting and tearing down piped
  loggers.  The piped loggers will receive a SIGTERM signal
  during shutdown.  There is a timing window where the SIGTERM
  signal is sent before APACHE is set up to handle this signal.
  This abend doesn't affect the server and it starts and runs
  with out an issue.
  MVS system log shows:
  S IHSAPACH
  IEF695I START IHSAPACH WITH JOBNAME IHSAPACH IS ASSIGNED TO
  USER IHSAPACH, GROUP IHSSERV
  BPXP023I THREAD 2BD1100000000001, IN PROCESS 50334135, WAS
  TERMINATED BY SIGNAL SIGTERM, SENT FROM THREAD
  2BD1080000000000, IN PROCESS 83888566, UID 41100, IN JOB
  IHSAPACH.
  IEF450I IHSAPACH *OMVSEX - ABEND=SEC6 U0000 REASON=0000FF0F
  BPXM023I (IHSAPACH) IHS is active.  Use jobname IHSAPACH for
  MVS commands.
  BPXM023I (IHSAPACH) CRIHS0001I IHS BPX.TCP.DOJ.GOV is active.
  83888566 *:8040 unspecified:-1. Use jobname IHSAPACH for
  console commands.
  keywords: abendSEC6 SEC6 EC6 RCFF0F RC0000FF0F
  

Local fix

• This abend doesn't cause an issue.  But if you'd like this to
  stop happening during server startup, do not use rotatelogs.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM HTTP Server on z/OS            *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND EC6 seen at startup with          *
  *                      rotatelogs configured.                  *
  ****************************************************************
  * RECOMMENDATION:  Apply this fix if EC6 is being reported     *
  *                  at                                          *
  *                  startup with no other outward symptom       *
  ****************************************************************
  On some systems, rotatelogs may receive a SIGTERM before it
  gets far enough in its own initialization to block it. This
  window is unpredictable as it is prior to the invocation of
  rotatelogs main() procedure, in LE processing.
  

Problem conclusion

• The server was updated to launch piped loggers named
  "rotatelogs" with the SIGTERM signal blocked, which
  eliminates
  the window where SIGTERM is unblocked.
  
  The fix for this APAR is targeted for inclusion in 9.0.0.11
  

Temporary fix

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