[asterisk-bugs] [Asterisk 0016081]: [patch] utils.c:938 ast_carefulwrite: Timed out trying to write causes corruption to astdb
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Nov 7 07:57:11 CST 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16081
======================================================================
Reported By: aragon
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16081
Category: Resources/res_agi
Reproducibility: have not tried
Severity: major
Priority: normal
Status: acknowledged
Target Version: 1.4.28
Asterisk Version: SVN
JIRA: SWP-286
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-10-15 10:02 CDT
Last Modified: 2009-11-07 07:57 CST
======================================================================
Summary: [patch] utils.c:938 ast_carefulwrite: Timed out
trying to write causes corruption to astdb
Description:
Agent addmember to local extensions causes the agent to be logged as
non-existent channels when ast_carefulwrite times out during login.
[Oct 15 10:40:07] NOTICE[29962]: utils.c:938 ast_carefulwrite: Timed out
trying to write
[Oct 15 10:40:07] NOTICE[29962]: utils.c:938 ast_carefulwrite: Timed out
trying to write
Here is an example of the corruption where the same local extension is
logged twice. The "outgoing" agent cannot logoff unless I manually remove
from astdb. The local agent can logoff but since the outgoing cannot calls
entering queue fail to reach agents and the local channel cannot log back
in.
Local/3345 at queuefifteen-outgoing/n (dynamic) (Invalid) has taken no calls
yet
Local/3345 at queuefifteen-agent/n (dynamic) (Not in use) has taken 2
calls (last was
1915 secs ago)
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014843 1 in 3 incoming zap PRI calls do no hea...
======================================================================
----------------------------------------------------------------------
(0113367) jvandal (reporter) - 2009-11-07 07:57
https://issues.asterisk.org/view.php?id=16081#c113367
----------------------------------------------------------------------
Can it be a "timeout" caused by AGI script when it start ? I'm currently
converting most of our AGI to use FastAGI in order to have a "persistant"
process instead of spawn a new process on each AGI call, maybe the problem
is that the AGI take some time to "initialize" ?
Issue History
Date Modified Username Field Change
======================================================================
2009-11-07 07:57 jvandal Note Added: 0113367
======================================================================
More information about the asterisk-bugs
mailing list