On Tue, Dec 16, 2014 at 1:04 PM, Jerry Geis <[email protected]> wrote: > > I am running a heartbeat... Asterisk 11.15.0 - same behaviour is noticed > on 1.4.43 also > > I issue a call through the API that does the below. just UserEvent and > Hangup > > -- Executing [s@heartbeat:1] UserEvent("Local/s@heartbeat-0000000f;2", > "HeartBeat, Noop") in new stack > -- Executing [s@heartbeat:2] Hangup("Local/s@heartbeat-0000000f;2", > "") in new stack > == Spawn extension (heartbeat, s, 2) exited non-zero on > 'Local/s@heartbeat-0000000f;2' > [Dec 16 13:57:01] ERROR[1956]: utils.c:1440 ast_careful_fwrite: fwrite() > returned error: Broken pipe > > > I get "many" broken pipes (last line above) in the > /var/log/asterisk/messages file. > Is there a way to more correctly close and not get that message? > > Assuming you are talking about the Asterisk Management Interface (AMI).
I have seen many broken pipe messages cause by the AMI client closing the connection before reading the response from the server. Some of the Asterisk Munin-Node plugins suffered from this problem. After you issue your command, you need to read the response. You should get a line that says '--END COMMNAD--' or an error response. Since the dialplan is executing, I doubt you will get an error. Your client should issue a Logoff action, then read all the responses until it gets the 'Thanks for all the fish.' response. Then close the socket.
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
