| Summary: | ASTERISK-00915: deadlock for unknown reason | ||
| Reporter: | Matt Florell (mflorell) | Labels: | |
| Date Opened: | 2004-01-26 11:44:15.000-0600 | Date Closed: | 2004-09-25 02:55:35 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) gdb_output_2004-01-26.txt | |
| Description: | I am still experiencing deadlocks about once a day at a random time on one Asterisk server. I have been unable to diagnose what is causing the problem. the gdb trace is attached. If anyone can point me to the process that may be causing this I would be very appreciative. As more crashes happen I will post the gdb dumps here. ****** ADDITIONAL INFORMATION ****** this is the definition of a deadlock: http://www.voip-info.org/tiki-index.php?page=What+is+a+deadlock | ||
| Comments: | By: Brian West (bkw918) 2004-01-28 00:22:00.000-0600 What hardware do you have and to what extent do you use queues, agents and such? What network card and zaptel cards do you have in this machine? What distro and gcc version? By: Mark Spencer (markster) 2004-02-08 15:20:10.000-0600 Can you update to latest CVS and see if this problem goes away? If it doesn't, can you produce a *new* "thread apply all bt"? By: Matt Florell (mflorell) 2004-02-09 09:30:52.000-0600 This seems to be related to this bug: http://bugs.digium.com/bug_view_page.php?bug_id=0000861 because since I stopped using remote manager interface connections, the server has stopped hanging. | ||