IJ32038: WORK AROUND SYSTEMD CONNECTION TIME OUT DURING REBOOT

APAR status

• Closed as program error.

Error description

• There appears to be an issues at
  the systemd layer that causes startup
  service to fail with connection time
  out during reboot.  If auto load
  is set to yes, GPFS may not be
  able to start up or it may get stuck waiting
  for the environment to be initialized.
  

Local fix

• Manually restart GPFS
  

Problem summary

• There appears to be an issues at
  the systemd layer that causes startup
  service to fail with connection time
  out during reboot.  If auto load
  is set to yes, GPFS may not be
  able to start up or it may get stuck waiting
  for the environment to be initialized.
  

Problem conclusion

• Benefits of the solution:
  Reduce a chance that GPFS may not
  startup or get stuck waiting for
  the environment to be initialized due
  to a systemd time out during reboot.
  
  Work Around:
  Manually restart GPFS
  
  Problem trigger:
  This issue affects cluster with auto
  load set to yes and hitting systemd
  connection time out during reboot.
  
  Symptom:
  GPFS does not start after a reboot
  
  Platforms affected:
  ALL Linux OS environments.
  
  Functional Area affected:
    GPFS startup
    CCR/systemd
  
  Customer Impact:
      High
  

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:

  IJ32186

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels