[asterisk-bugs] [JIRA] (ASTERISK-28028) Disk I/O error, dropped calls
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Aug 29 09:30:54 CDT 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-28028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244641#comment-244641 ]
Asterisk Team commented on ASTERISK-28028:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
> Disk I/O error, dropped calls
> -----------------------------
>
> Key: ASTERISK-28028
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28028
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_rtp_asterisk
> Affects Versions: 15.5.0
> Environment: FreePBX Distro 14.0.3.11. (Red Hat).
> Reporter: basildane
>
> Several times a day, an incoming call rings once and is immediately dropped.
> The log shows:
> WARNING[6716][C-0000004e] res_rtp_asterisk.c: RTP Read error: Bad file descriptor. Hanging up.
> [...]
> WARNING[2671] db.c: Error executing SQL (COMMIT): disk I/O error
> WARNING[2671] db.c: Error executing SQL (ROLLBACK): cannot rollback - no transaction is active
> I have done consistency checks on the MariaDB databases, checked everything I can think of on the disk itself. I can not find any cause.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list