[Home]

Summary:ASTERISK-14473: Asterisk 1.4.26-rc6 revision 202945 locked in cdr.c line 1060 (post_cdr)
Reporter:David Brillert (aragon)Labels:
Date Opened:2009-07-15 13:49:00Date Closed:2011-06-07 14:00:51
Priority:MajorRegression?No
Status:Closed/CompleteComponents:CDR/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) revision202945cdr.c_locked.txt
Description:Hundreds of locks on cdr.c on very busy system

****** ADDITIONAL INFORMATION ******

revision202945cdr.c_locked.txt uploaded
This file displays core show locks and thread apply all bt pid of Asterisk

This system is very busy under hammer tests so I am not sure if this actually a bug or the problem is caused by load.  It does occurr to me though that the high load may be caused by the locks.

Also in the CLI there are a lot of these ERROR messages (and these consistently occur on a less busy system in my deployment tests).  I don't think these specific errors are caused by load issues.
[Jul 15 14:41:55] ERROR[17845]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
[Jul 15 14:42:06] ERROR[17892]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
Comments:By: Tilghman Lesher (tilghman) 2009-07-15 14:33:15

This lock is actually caused by a freeze deep within mysql driver code, and it's nothing that we can really help, since it's in 3rd party code.  Have you tried upgrading to the very latest mysql client code?  That typically fixes such problems.  If not, then this problem needs to be reported to the MySQL project.
By: David Brillert (aragon) 2009-07-15 15:06:57

Looks like I could use an upgrade, but I will certainly have to do some sanity checks on my sql integration.
[root@sip ~]# rpm -qa |grep mysql
mysql-5.0.45-7.el5

Looks like the current version is 5.0.83-0
By: David Brillert (aragon) 2009-07-15 15:23:11

tilghman, where do you think these errors are coming from?
[Jul 15 14:42:06] ERROR[17892]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
By: Tilghman Lesher (tilghman) 2009-07-15 15:55:19

Probably manager.  It's likely a connection was dropped, since this message is what appears when that happens.  In the past, the same problem occurred; we just didn't report it.
By: David Brillert (aragon) 2009-07-20 08:37:28

administrator can close this ticket.
The locks are caused by excessive CPU load.
By: Leif Madsen (lmadsen) 2009-07-20 14:04:18

Closed per reporter.