Summary: | ASTERISK-04571: "file.c: No such format" causes Asterisk to crash | ||
Reporter: | Denis Voitenko (denis) | Labels: | |
Date Opened: | 2005-07-12 18:26:24 | Date Closed: | 2011-06-07 14:10:09 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Whenever Asterisk encounters "file.c: No such format" error it simply quits. I haven't done any debugging on this as my glibc is stripped, but here's an output from debug. Jul 12 18:16:14 DEBUG[11727] channel.c: Scheduling timer at 0 sample intervals Jul 12 18:16:14 DEBUG[11727] channel.c: Scheduling timer at 0 sample intervals Jul 12 18:16:14 WARNING[11727] file.c: No such format 'wav|wav' Jul 12 18:16:14 WARNING[11727] res_monitor.c: Could not create file /usr/local/asterisk/var/spool/monitor/1121206536.101-in | ||
Comments: | By: Kevin P. Fleming (kpfleming) 2005-07-12 18:28:10 It obviously did not 'quit', as you got further messages. Please describe exactly what you mean, and retest with _current_ CVS HEAD, since yours is nearly two months old. By: Russell Bryant (russell) 2005-07-17 19:13:03 Maybe he means that the call quits... The Montior application will return -1 if it fails to be able to start monitoring on the channel. I'm not sure if this is desired behavior. Maybe we should have the Monitor application set a status variable indicating its success and have it always return 0. By: Denis Voitenko (denis) 2005-07-18 09:22:11 When I said "simply quits" I meant "crashes with nothing in the logs to say it's crashing". By: Russell Bryant (russell) 2005-07-18 10:04:36 crashing, as in, Asterisk ceases to run? Are you getting a segmentation fault? If so, we need to get a backtrace. At a minimum, we need the necessary configuration to recreate the issue. By: Clod Patry (junky) 2005-07-18 11:41:38 Plus, i'd like to see that part in your extensions.conf. Add output of: # ls -l /usr/local/asterisk/var/spool/monitor/ Join CLI's output too. We need more infos that just what you gave us denis. The more info you can give, the faster your problem will be fixed. Thanks. By: Michael Jerris (mikej) 2005-07-26 23:49:32 Unfortunately, we are unable to provide any assistance on this bug without further information. Can you please provide the requested information and re-open the bug when it is ready. Thanks |