Benign 'Broken pipe' and 'Failed to write to response stream' errors in healthd.log

Products

• VMware vSphere ESXi

Issue/Introduction

On VMware ESXi, the following error messages appear frequently in /var/run/log/healthd.log.

[timestamp] Er(163) healthd[######]: [Originator@#### sub=healthdEndpoint.HTTPService] Failed to write to response stream; <io_obj p:0x000000######, h:##, <UNIX 'vmwLocalSocketHealthd'>, <UNIX ''>>, N7Vmacore15SystemExceptionE(Broken pipe: The communication pipe/socket is explicitly closed by the remote service.)
[timestamp] Er(163) healthd[######]: --> [context]###################################[/context]
[timestamp] Er(163) healthd[######]: [Originator@#### sub=HealthdHandler] Failed to write to response stream : System exception while transmitting HTTP Response:
[timestamp] Er(163) healthd[######]: --> error id = 32
[timestamp] Er(163) healthd[######]: -->

Cause

Broadcom is investigating the root cause of this issue.
If you require support, please submit a support request and a log bundle with trivia logging enabled and the error is occurred.

How to enable trivia logging:

1. Connect to ESXi via SSH.
2. Execute the following command
   
   configstorecli config default get -c esx -g health -k healthd > config.json
   
   
3. Edit the output config.json file using a command such as vi
   
   Before change)
   

      "log": {
         "directory": "/var/run/log/",

   
   
   After change)
   

      "log": {
         "directory": "/var/run/log/",
         "level": "trivia",

   
   
   
4. Execute the following commands
   
   configstorecli config current set -c esx -g health -k healthd -infile config.json
/etc/init.d/health restart
rm config.json

Resolution

This log statement is benign.
It simply indicates the sender of the HTTP request exited without waiting for a successful 200 OK response from the server (the healthd service) and be ignored safely.