write() returned error: Broken pipe on each autocall

[omar]

Hi

For every successfully auto call, the asterisk cli always show the following error:

ERROR[9869]: utils.c:967 ast_carefulwrite: write() returned error: Broken pipe

What does it mean?

_____________________________________________________________________________________________________
The environment is
1 DB
1 WWW
1 ARCHIVE SERVER
2 asterisk dialers (astA, astB)

vicibox 3.1.15
asterisk 1.4.39.2 (both servers)
vicidial 2.6b0.5
build 120831-1523

All the servers have the same version and build

[DomeDan]

This has been asked a few times before, a simple google search will direct you to any of them, like this one http://www.vicidial.org/VICIDIALforum/v ... =8&t=15275

[omar]

This has been asked a few times before, a simple google search will direct you to any of them, like this one http://www.vicidial.org/VICIDIALforum/v ... =8&t=15275

Thanks for the answer

Until now, searching this topic in different post. There are just to kind of answers:

U can safely Ignore them.

Please open a new topic if you are going to discuss something different.

Also, I would recommend trying svn/trunk to see if the same issue exists.

I know there were a couple schema hiccups in the past, but none since the last branch.

That is Asterisk complaining that it cannot send a message to either and AGI script or something that is connected to the Manager interface. This is because the item in question has already exited. These are normally completely harmless and really should not be an error, more like a warning, but the asterisk development team doesn't see it that way. In any even you are most likely fine unless you are having other problems. We have fixed most of these "Errors" in Vicidial SVN trunk (still working on one more), but like I said they should be harmless..

So, this error is normal? and I just have to ignore it?
BUT if I don't missunderstood, Matt says that this error shouldn't be in the last branch

i will still searching to find the right answer, and if i have success i will post the solution or answer on this post.

Thanks

[williamconley]

the link provided by DomeDan has specific detailed responses. Perhaps you should read through it again?

viewtopic.php?f=8&t=15275

[mcargile]

The funny thing is that that forum post does not actually list the real problem.

First off some back ground. At some point Digium changed the behavior of the Manager interface and the AGI interface. You used to be able to issue commands and not stick around for the results. Matt used to connect into the AMI, issue a command, and then immediately disconnect. After Digium made the change this error would fly by on the screen. We then added something that would wait up to four seconds for a response and then disconnect. This cut the number of these errors down dramatically. However they still appear.

It was not until I started doing Asterisk 1.8 development that I was able to figure out where the rest of these are coming from. In some of the AGI scripts Matt is not using the AGI perl object to issue AGI commands. Instead he is issuing them directly. The problem is he is not grabbing the response back from Asterisk and just exiting. This is resulting in the broken pipe errors. Luckily Asterisk is perfectly happy to just throw the error and chug along. My Asterisk 1.8 patches have this fix in them, which will also fix it for Asterisk 1.4.

[omar]

the link provided by DomeDan has specific detailed responses. Perhaps you should read through it again?

http://www.vicidial.org/VICIDIALforum/v ... =8&t=15275

Hi

In that topic or any other that i found, MATT never says something like: "The error is normal and you can ignore it". OR "If you don't want that ERROR message you can change it to a WARNING message, following....". For matt the ERROR message shouldn't be there in SVN/TRUNK code.

And as matt is the main creator of vicidial, he is the authorized voice to give a final conclusion.

Thanks

[mcargile]

While I am not Matt, with regards to Vicidial, that error is normal and you can ignore it. If you are using the asterisk box for other things that control Asterisk programatically, you might want to double check the code is waiting for Asterisk to respond. I would not recommend changing it to a WARNING however. If you can be patient for a few months this will go away completely when my asterisk 1.8 patches are mainlined.