| Summary: | ASTERISK-08366: Meetme conference application randomly crashing with app_meetme.c errors | ||
| Reporter: | Jay Dutt (jdutt) | Labels: | |
| Date Opened: | 2006-12-18 09:13:10.000-0600 | Date Closed: | 2007-03-26 12:53:56 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_meetme |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace.txt ( 1) messages | |
| Description: | Our conference system (only) pbx, which only runs meetme and no other asterisk function, is randomly crashing. Crash occurs once every few days, and occurs regardless of traffic (sometimes crashes on Sunday night when there is no conf participants. The following types of messages seem to be logged prior to the crashes: Dec 14 08:15:09 WARNING[25286] app_meetme.c: Conference not found Dec 15 10:05:54 WARNING[27675] app_meetme.c: Failed to write audio data to conference: Bad file descriptor Dec 15 10:06:03 WARNING[27673] app_meetme.c: Failed to write audio data to conference: Inappropriate ioctl for device Dec 15 10:10:02 WARNING[27673] app_meetme.c: Failed to write audio data to conference: Invalid argument Dec 15 10:10:02 ERROR[27673] app_meetme.c: Bad! Bad! Bad! user->nextuser is NULL but we're not the end! Dec 15 10:12:18 WARNING[27675] app_meetme.c: Failed to write audio data to conference: Invalid argument Dec 15 10:12:18 ERROR[27675] app_meetme.c: Bad! Bad! Bad! user->nextuser is NULL but we're not the end! Dec 17 21:16:52 WARNING[26620] app_meetme.c: Failed to write audio data to conference: Bad file descriptor Dec 17 21:19:19 WARNING[26620] app_meetme.c: Failed to write audio data to conference: Inappropriate ioctl for device We're running on asterisk 1.2.13. This is a major customer so we need to find a solution asap. Thanks. (Full log is attached, winzip'd) | ||
| Comments: | By: Serge Vecher (serge-v) 2006-12-18 10:09:17.000-0600 any difference with recently released 1.2.14? By: Jay Dutt (jdutt) 2006-12-18 11:39:00.000-0600 We have not tried 1.2.14 yet. Do you think this will make a difference? Thanks. By: Serge Vecher (serge-v) 2006-12-18 12:19:03.000-0600 it's hard to say for sure, since the messages file attached does not contain much useful information, but there was one fix for meetme that went in to 1.2.14. By: Jason Parker (jparker) 2006-12-26 15:34:53.000-0600 Are you able to upload a backtrace when this happens? By: louietarpo (louietarpo) 2007-02-06 12:12:23.000-0600 We have been having the same issue intermittantly from the 1.0.x series. Our console output is similar. I was able to capture a core dump from yesterday's crash. Uploaded backtrace.txt. We are running Asterisk 1.2.13, Zaptel 1.2.7, libpri 1.2.4, asterisk addons 1.2.5. By: Serge Vecher (serge-v) 2007-03-07 11:30:52.000-0600 I really need you to test with the 1.2.16 release, the changes in r.55750 have fixed a lot of random crashes. By: louietarpo (louietarpo) 2007-03-08 10:41:04.000-0600 Acknowledged. I'll add the Asterisk upgrade to the next maintenance window. By: Serge Vecher (serge-v) 2007-03-26 12:53:56 if still an issue with 1.2.17, please reopen the issue with a new backtrace. | ||