PI61446: POTENTIAL SYSLOGD HANG AFTER PERFORMING A SIGHUP

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible.

Error description

• The potential exists for the SYSLOGD process to become
  unresponsive after sending a SIGHUP to perform a refresh of the
  configuration.  This in turn will propagate to other processes
  when they invoke the syslog() service.  Observed symptoms
  include:
  
   - The primary symptom will be EDC6257C THERE IS A SOCKET
     PROBLEM, SYSLOGD MAY NEED TO BE RESTARTED messages.
  
   - If FTPLOGGING or any DEBUG options are enabled in the FTP
     server, users may not get a response to connection attempts.
     This will also cause a larger than normal number of FTPDx
     address spaces, potentially causing a IEA602I ADDRESS SPACE
     CREATE FAILED condition.
  
   - If any debug or trace options are enabled in OMPROUTE, this
     could cause continual adjacency failures (EZZ7921I and
     EZZ7968I messages).
  
   - In some conditions, it can cause SYSLOGD to issue a 'FSUM1223
     Error 79/D1201DA ...' message, followed by an ABEND.
  

Local fix

• - Recycle SYSLOGD.
  
   - If using the older method of creating daily log files by
     issuing a SIGHUP at midnight and having a date substitution
     characters (%Y, %m, or %d) in the file name, convert to using
     the builtin SYSLOGD archival options.  See
     https://ibm.biz/Bd4n6R for more information.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server for z/OS Version  *
  * 2 Release 1 IP: syslog daemon (syslogd)                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The syslog daemon address space hung after receiving a       *
  * SIGHUP signal.                                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the PTF.                                               *
  ****************************************************************
  The SIGHUP signal causes syslogd to enter restart processing.
  The restart processing is interfering with syslogd's automatic
  archival processing.  Even when the automatic archival function
  is not configured, the associated process is always running and
  performing other time related tasks.  So, depending on the
  timing of the SIGHUP signal, the problem can still occur.
  

Problem conclusion

• syslogd has been changed to correct the interference between
  restart processing that is driven by a SIGHUP signal, and other
  syslogd processes.
  

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:

  UI38431

Modules/Macros

• EZASLOGD
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R210 PSY UI38431

     UP16/07/09 P F607

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.