[asterisk-bugs] [Asterisk 0014379]: AMI shows utils.c:1198 ast_careful_fwrite: fflush() returned error: Broken pipe
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Feb 4 17:12:06 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14379
======================================================================
Reported By: chris-mac
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 14379
Category: Core/ManagerInterface
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 172030
Request Review:
======================================================================
Date Submitted: 2009-01-31 16:50 CST
Last Modified: 2009-02-04 17:12 CST
======================================================================
Summary: AMI shows utils.c:1198 ast_careful_fwrite: fflush()
returned error: Broken pipe
Description:
When sending data to AMI socket, without reading (waiting for) response -
console shows:
ERROR[5148]: utils.c:1198 ast_careful_fwrite: fflush() returned error:
Broken pipe
How to reproduce:
0. You will need php5-cli installed
1. Download 'AMI.class.php' and 'ami-test.php' attached.
2. Edit AMI username/password in 'ami-test.php'.
3. Run ./ami-test.php
4. Watch Asterisk console
NOTE: To revert back to a 'normal' behaviour, change line 72 of
'AMI.class.php' to: 'public $sync = true;'
======================================================================
----------------------------------------------------------------------
(0099464) khratos (reporter) - 2009-02-04 17:12
http://bugs.digium.com/view.php?id=14379#c99464
----------------------------------------------------------------------
Maybe the problem is a little bigger for us (php users) than just a 'broken
pipe' message, because it also means that changes intended to be done with
'UpdateConfig' command will NOT be written to the destination files after
'broken pipe' messages start to appear.
That is, if you make several changes to a the same file using
updateconfig, after the first 'broken pipe' changes are not written.
I was testing with sockets created with fsockopen (socket based stream)
and socket_create(AF_INET, SOCK_STREAM, SOL_TCP) also called 'endpoint of
communication' and both are broken.
Issue History
Date Modified Username Field Change
======================================================================
2009-02-04 17:12 khratos Note Added: 0099464
======================================================================
More information about the asterisk-bugs
mailing list