Broken Pipe Errors

[Rick Brown]

Broken Pipe Errors

When you recieve a broken pipe warning, it usually means that a command was sent to the engine (pstop, for example) and hcicmd timed out and disconnected before the engine could send a response. When the engine gets around to sending the response, it gets a SIGPIPE.

You may see a message like “command client timed out – assuming process is hung”

If you see the “broken pipe” messsages the engine is *not* hung, it is just busy. It is not a major problem, however you may want to determine why the engine is so busy – normal circumstances it should service the command within the timeout (30 +/- seconds)

Rebuilding ICL libraries

TCP/IP ERROR: PANIC: Calling “dbi shutdown” for thread xx_xxx Write on socket 18 failed :BROKEN PIPE

[icl.tcpi.ERR/0: dft_xlate] Write on socket 19 failed: Broken Pipe

Process keeps crashing.

FIX or WORKAROUND: the icl files must be rebuilt with hcidbinit -i

Topic