IJ49715: RPC.STATD NOT RUNNING IN PROTOCOL NODES

APAR status

• Closed as program error.

Error description

• The 'rpc.statd' may be terminated or experience a crash due to
  statd-related issues.In these instances, the NFSv3 client will
  relinquish control over NFSv3 exports,and the GPFS health
  monitor will indicate 'statd_down'.
  

Local fix

Problem summary

• The 'rpc.statd' may be terminated or experience a crash due to
  statd-related issues.In these instances, the NFSv3 client will
  relinquish control over NFSv3 exports,and the GPFS health
  monitor will indicate 'statd_down'.
  

Problem conclusion

• This problem is fixed in 5.1.9.2
  To see all Spectrum Scale APARs and their respective
  Fix solutions refer to page:
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
  apars.html
  
  Benefits of the solution:
  Fixed the code to restart 'rpc.statd' if it is not running on
  the protocol.This will help NFSv3 clients regain access to mount
  points.Introduced a new configuration parameter to automatically
  restart the 'rpc.statd' process if it is not running on the
  protocol node.Add "restartrpcstatd = true" in
  /var/mmfs/mmsysmon/mmsysmonitor.confto enable this feature.
  
  Work Around:
  None
  
  Problem trigger:
  'rpc.statd' gets crashed or stopped by an external
  process.
  
  Symptom:
  The GPFS health monitor will show 'statd_down' warning and NFSv3
  client lose control over NFSv3 exports.
  
  Platforms affected:
  Linux Only
  
  Functional Area affected:
  NFS
  
  Customer Impact:
  Suggested
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels