[asterisk-users] Broken Pipe error while using UpdateConfig command

[Tilghman Lesher]

On Friday 06 March 2009 03:02:30 pm Randy Paries wrote:
> On Tue, Feb 3, 2009 at 2:58 PM, Jose P. Espinal <jpe at slackware-es.com> 
wrote:
> > Hello List,
> >
> > I have been working on a little PHP software that uses AMI's
> > UpdateConfig command in order to modify some of it's config files.
> >
> >
> > I was working with 'Asterisk 1.4.22.1' and everything was working.
> > After upgrading to 'Asterisk 1.4.23.1' I receive a lot of errors of the
> > type:
> >
> >
> > ERROR[11505]: utils.c:966 ast_carefulwrite: write() returned error:
> > Broken pipe
> >
> >
> > I'm completely sure that I did not modify anything on the PHP script,
> > in fact, I test it on the older version of Asterisk mentioned above
> > and it still works like a charm.
> >
> > Can someone point me out about a possible place to start looking for
> > this error?
> >
> >
> > NOTE:
> > An interesting thing to note is that I sent all the commands that my
> > script executes on the AMI to a file (/tmp/debug.txt )
> >
> > Then copying all the file content into AMI interface directly ( telnet
> > [server_ip] 5038) and it executed all the commands without any problems.
>
> So is there any news on this issue?
>
> I am seeing the same thing. I am new to the AGI world and just
> starting to do some coding and started getting these errors.
> I was not sure if it is something i am doing wrong or not.

Yes, it was determined on the bugtracker that the OP was not waiting for
Asterisk to return a response, but instead closing the connection prematurely.
This explains why when he concatenated the text to the manager port, it all
worked correctly.  We advised him to use the manager port interactively,
instead of pushing the set of commands and closing the port too soon.  With
current connections, once Asterisk can no longer respond, it assumes that
the remote client is no longer interested in interaction and shuts down its
processing, as well.  This in turn saves server resources, especially when
clients do not shut down the connection properly (like when they crash).

-- 
Tilghman