IJ52514: REWORD "MMSYSMONC: SOCKET WAS CLOSED WHILE RECEIVING DATA" TO AVOID MISUNDERSTANDINGS AND STATE THE ROOT CAUSE

APAR status

• Closed as program error.

Error description

• Currently if any request to mmsysmon.py times out, the customers
  get this error message, which is hard to understand and also
  does not state the fact, that we have reached the timeout.
  

Local fix

Problem summary

• Currently if any request to mmsysmon.py times out, the customers
  get this error message, which is hard to understand and also
  does not state the fact, that we have reached the timeout.
  

Problem conclusion

• This problem is fixed in 5.2.1.1
  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:
  Customers would get know the request to mmsysmon.py was timeout
  while executing.
  
  Work Around:
  None
  
  Problem trigger:
  Any command that requests mmsysmon.py whould be timedout. eg.
  "mmsysmonc --wait 1 noderoles refresh".  this command would be
  timed out as this is a long-running command with a timeout of 1
  sec.
  
  Symptom:
  "mmsysmonc: socket was closed while receiving data" can be seen
  in output.
  
  Platforms affected:
  Linux Only
  
  Functional Area affected:
  perfmon (ZIMON)
  
  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