IJ13067: CONFIGRM STARTUP ERROR IN POWERHA CLUSTERS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When IBM.ConfigRM is initializing after a reboot in a
  PowerHA cluster, while checking for the existence of a
  TieBreaker definition, there is a small chance of causing
  content under /var/ct to be set up incorrectly, which
  will then cause a startup error for ConfigRM.
  
  Whether a TieBreaker is actually defined does not alter
  the outcome; the problem occurs when checking whether
  one exists or not.
  
  A CONFIGRM_ERROR_ER will appear in the errpt, and related
  traces in ConfigRM at that time will show:
   12/01/18 15:28:41.980800 T(  1) _CFD
  id=0xffffffffError 98305 was returned from
  "ConfigRM::main()" on line 598 in file "
  ../../../../../src/rsct/rm/ConfigRM/IBM.ConfigRMd.C".
                Message=2645-000 Operation failed due to
  error 17 returned from symlink(3ZBUFGRE
  uHvu034i~vHXzc,/var/ct/vv501601) returns rc=-1, errno=17.
  

Local fix

Problem summary

• During bootup initialization, there is a small chance of an
  error being hit by ConfigRM while checking for the existence
  of a TieBreaker in the configuration.  (The error can occur
  whether or not a TieBreaker is actually configured.)
  Most of the time, ConfigRM will be restarted and eventually
  able to bring things online, so only the error messages will
  indicate what happened during startup.
  .
  In rare cases, depending on the timing, the delay in the
  RSCT layer might prevent PowerHA from coming online, even if
  it is supposed to start automatically at boot time.  (This
  will be slightly more likely if a TieBreaker is configured.)
  

Problem conclusion

• Initialization handling has been corrected to avoid the error.
  

Temporary fix

• If PowerHA is left offline after a reboot as a result of this
  error, check the state of the IBM.ConfigRM subsystem
  (lssrc -s IBM.ConfigRM).  If it is inoperative, you can try
  to start it manually by running "startsrc -s IBM.ConfigRM".
  If ConfigRM remains active, check the "lsrpdomain" command.
  .
  If ConfigRM does not remain active, or if "lsrpdomain"
  continues to report offline even after several minutes,
  you will need to collect data and contact IBM support.
  .
  Once "lsrpdomain" is reporting online, you can try to start
  PowerHA cluster services using the normal documented commands.
  

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

  RSCT FOR AIX

• Fixed component ID

  5765F07AP

Applicable component levels

• R323 PSY U889770

     UP21/09/02 I 1000

PTF to Fileset Mapping

• U887098 rsct.basic.rte 3.2.3.5

• U885259 rsct.basic.rte 3.2.3.4

• U885259 rsct.basic.rte 3.2.3.4

• U885259 rsct.basic.rte 3.2.3.4

• U887098 rsct.basic.rte 3.2.3.5

• U887098 rsct.basic.rte 3.2.3.5

• U889770 rsct.basic.rte 3.2.3.6

• U889770 rsct.basic.rte 3.2.3.6

• U889770 rsct.basic.rte 3.2.3.6