topic Re: Finding the RC of broken pipe in Administration and Deployment

Finding the RC of broken pipe

dkoggerson — Mon, 13 Jun 2022 15:42:30 GMT

\Desktop\Logs\ObjectSpawner_2022-06-13_awasprppd053_5186.log (15 hits)

Line 318563: 2022-06-13T02:30:11,807 WARN [01164118] :sasevs@saspw - The TCP/IP tcpSockWrite() support routine failed with error 32 (Broken pipe).

Line 538403: 2022-06-13T05:10:06,268 WARN [01183708] :sasevs@saspw - The TCP/IP tcpSockWrite() support routine failed with error 32 (Broken pipe).

Line 538427: 2022-06-13T05:10:21,868 WARN [01183732] :sasevs@saspw - The TCP/IP tcpSockWrite() support routine failed with error 32 (Broken pipe).

Line 538442: 2022-06-13T05:10:25,585 WARN [01183748] :sasevs@saspw - The TCP/IP tcpSockWrite() support routine failed with error 32 (Broken pipe).

Re: Finding the RC of broken pipe

SASKiwi — Mon, 13 Jun 2022 20:00:24 GMT

The "return code" of the error in this case is the error number, 32. What's your actual question? Posting a server process log without any supporting information as to what service it belongs to on what SAS server and under what circumstances this happened is not particularly helpful. You should also include the SAS version you are using and what OS it is running on.

Re: Finding the RC of broken pipe

gwootton — Tue, 14 Jun 2022 13:53:19 GMT

If by "RC" you mean "root cause", this "Broken Pipe" message looks to be occurring between the Object Spawner and SAS Environment Manager Agent, probably the agent on the middle tier confirming the Object Spawner is up and running. I might start by checking the Environment Manager Agent logs on the middle tier to see if you see any matching failures there, and the system/event logs on those two hosts for issues with the network layer.