| Summary: | ASTERISK-20087: Asterisk gives "Broken pipe" warning on hangup | ||||
| Reporter: | David Cunningham (dcunningham) | Labels: | |||
| Date Opened: | 2012-07-03 07:42:46 | Date Closed: | |||
| Priority: | Minor | Regression? | |||
| Status: | Open/New | Components: | Core/General | ||
| Versions: | 1.8.11.1 13.18.4 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | CentOS release 5.6 (Final) | Attachments: | ( 0) extensions_phone.conf ( 1) extensions_product_18.conf ( 2) extensions.conf.txt ( 3) trace.txt ( 4) trace-20087.txt | ||
| Description: | In an Asterisk log we see: <SIP/product-local-000051a8>AGI Tx >> HANGUP <SIP/product-local-000051a8>AGI Tx >> HANGUP [Mar 5 18:05:55] ERROR[14365]: utils.c:1164 ast_carefulwrite: write() returned error: Broken pipe From testing, it appears the "Broken pipe" error is due to the second HANGUP not being read by the AGI. The question is, why does Asterisk send two HANGUP messages? Thanks for your help. | ||||
| Comments: | By: Paul Belanger (pabelanger) 2012-07-04 22:29:55.052-0500 Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker, http://www.asterisk.org/support. By: David Cunningham (dcunningham) 2012-07-04 22:53:21.334-0500 I believe the fact that Asterisk sends the HANGUP twice is a bug. Are you sure it's not? By: Matt Jordan (mjordan) 2012-07-09 08:18:33.279-0500 Re-opened. David: Please provide a full DEBUG log and your extensions.conf. Thanks, Matt By: David Cunningham (dcunningham) 2012-07-09 17:36:19.359-0500 Trace is attached. Here is the extensions.conf. Thanks! [Edit by Rusty Newton - attached config content as extensions.conf.txt] By: Rusty Newton (rnewton) 2012-07-10 16:48:16.908-0500 David, can you provide a asterisk "full" log with DEBUG and VERBOSE messages turned on in logger.conf? Verify they are at least level 5. Leave the AGI debug on as well. Attach to the issue as a text file. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: David Cunningham (dcunningham) 2012-07-10 18:51:25.198-0500 Asterisk SIP and AGI trace attached. By: David Cunningham (dcunningham) 2012-07-10 18:58:16.843-0500 Included extensions file. By: David Cunningham (dcunningham) 2012-07-10 18:58:39.276-0500 Included extensions file. By: David Cunningham (dcunningham) 2012-07-10 19:00:20.264-0500 Trace and the included extensions files attached. When getting the trace I could only get the error to occur when both: a) The call includes a Dial which creates a new AGI. b) The caller hangs up, not the called party. Thanks. By: Vladimir Latyshev (latysheff) 2012-10-08 09:59:27.069-0500 I can confirm this unwanted behaviour of Asterisk. "AGI Tx >> HANGUP" comes after "AGI Script agi://XXXXX completed, returning X" and rises the ERROR By: Vladimir Latyshev (latysheff) 2012-10-08 10:12:18.309-0500 Ok, done with it by setting Set(AGISIGHUP=no) in dialplan. Now it doesn't send HANGUP twice. By: Joshua C. Colp (jcolp) 2017-12-19 05:41:53.182-0600 Are you still experiencing this as a problem? I know of large users of AGI who have not seen this. By: David Cunningham (dcunningham) 2017-12-19 19:46:02.995-0600 We do still get it, but decided it was harmless and therefore not worth spending time on. Thank you. | ||||