PK75235: SENDMAIL STORAGE GROWTH WHEN RUNNING WITH PERSISTENT QUEUE RUNNER

APAR status

• Closed as fixed if next.

Error description

• The sendmail server is running with the -qp option so that it
  has a persistent queue runner.  With this set, you may see a
  storage growth in the asid for the persistent queue runner.  If
  the asid runs out of storage, may see these messages:
  sendmail[50725301]: m832QftD50725301: SYSERR(OMVSKERN): out of
  memory:
  sendmail[33948020]: restart queue runner=0 due to signal 0x4700
  m81DdYIM393822: SYSERR(OMVSKERN): out of memory:
  
  : restart queue runner=0 due to signal 0x4700
  
  : ERROR: persistent queue runner=0 restarted too many times,
  queue runner lost
  
  KEYWORDS: sendmail private subpool2 sp2 key8 k8
  .
  VERIFICATION STEPS:
  A dump will show a storage growth in subpool 2 key 8 filld with
  HANC control blocks.
  Running the queue runner with LE option:
   _CEE_RUNOPTS=HEAPCHK(ON,0,0,10)
  
  will produce a CEEDUMP that shows a traceback of the routines
  that is allocating the storage.  It will show many of these
  entries:
  CEEV#GH       228AED68  +00000000   CEEPLPKA
  fetchep       22AC13A8  +0000007A   CEEEV003
  atexit        229D6540  +00000278   CEEEV003
  sm_io_setvbuf
                22624AF8  +00000394   *PATHNAM
  openxscript   22676DC0  +00000172   *PATHNAM
  initsys       22677060  +00000060   *PATHNAM
  readqf        2269C3C8  +000006E4   *PATHNAM
  dowork        226A2960  +0000030C   *PATHNAM
  runner_work   2269BD00  +0000049C   *PATHNAM
  run_work_group
                226A3898  +00000A68   *PATHNAM
  

Local fix

• In the sendmail.cf file, after statement:
  O QueueDirectory=/var/spool/mqueue
  add:
  Qmqueue, F=f
  This will have sendmail fork to deliver mail, and when the
  forked process goes away, the storage is freed
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 8, 9 and 10    *
  *                 IP: Sendmail                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Sendmail shows storage growth when      *
  *                      using persistent queue runners in       *
  *                      configuration.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SENDMAIL storage growth when running with persistent queue
  runner selected in configuration file.
  
  The sendmail server is running with the -qp option so a
  persistent queue runner is active. With this set, you may
  experience storage growth in the asid for the persistent
  queue runner.  When a persistent queue runner is active,
  sendmail does not fork off threads to run the individual
  queues.  However, in some of it's utility routines contain
  calls to atexit() to setup cleanup routines for thread
  termination.  Multiple calls to atexit() causes the
  storage growth.
  
  Workaround by setting configuration option in the sendmail.cf
  file, after statement:
  O QueueDirectory=/var/spool/mqueue
  add:
  Qmqueue, F=f
  This will have sendmail fork to deliver mail, and when the
  forked process goes away, the storage is freed
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

Temporary fix

Comments

• This APAR is being closed FIN (Fixed If Next) with concurrence
  from the submitting customer. This means that a fix to this
  APAR is expected to be delivered from IBM in a release (if any)
  to be available within the next 24 months.
  
  This problem will be tracked as Feature F146487
  by Communications Server for z/OS Development.
  
  The solution for this APAR is included in CS for z/OS Version 1
  Release 12.
  

APAR Information

• 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

• R1A0 PSN

     UP

• R180 PSN

     UP

• R190 PSN

     UP