| Summary: | ASTERISK-19220: chan_sip deadlock | ||
| Reporter: | Sebastian Gutierrez (sum) | Labels: | |
| Date Opened: | 2012-01-19 20:48:34.000-0600 | Date Closed: | 2012-01-20 07:15:39.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | Frequency of Occurrence | Frequent | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) Debug.log | |
| Description: | chan_sip enter to a deadlock state, active calls are ok, but no new registrations allowed or new calls. I know this is on 1.6.2.20 and has no support, but this issue has been here forever and it seems to be the only one that makes 1.6.2 unstable, a patch would be great to at least have 1.6.2 stable, I tried moving to 1.8 but deadlocks are worst and can't be on production sites, I put don't optimize and debug threads on production with at least 200 sip phones calling, and when the deadlock appeared I dummped asterisk to get the bt, locks, and all info that is attached. | ||
| Comments: | By: Sebastian Gutierrez (sum) 2012-01-19 20:49:42.354-0600 diferent outputs after dump. core show locks, bt full, and others By: Matt Jordan (mjordan) 2012-01-20 07:15:31.552-0600 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8. By: Sebastian Gutierrez (sum) 2012-01-20 07:26:47.271-0600 this kind of response is making people moving away for asterisk... 1.6.2 has some deadlocks 1.8 has many deadlocks, imposible even to test on production with more than 10 phones, this issue is a way to have a patch altough never gets to the repo, for many people that has this issue and is not possible to upgrade. you are moving fast but not delivering a stable product, you can check the comments on the mailining list, and others, 1.4 is the last stable version if you check the community, I provided all necesary info to at least be looked at, I made a production site to run under don't optimize and debug threads to have this data, at least a polite answer was expected. | ||