[Home]

Summary:ASTERISK-09253: asterisk crash when there's no space left on a local device or when there are too many extensions to handle?
Reporter:Caio Begotti (caio1982)Labels:
Date Opened:2007-04-12 11:54:45Date Closed:2007-04-12 13:37:54
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I just installed the latest trunk code in a box with a 4gb sized partition and let it running for 2 hours then when I got back to the office Asterisk had crashed. I had 5 thousand extensions [not registered] in this box I don't know if this could affect the issue.

I believe that Asterisk should not crash like that with such log messages as you can read in the info box below. Other processes like from Apache and my MTA were fine, though.

I noticed that my PostgreSQL server was down too but still, Asterisk shouldn't have crashed, right? According to my Postgres log, it was Asterisk that made it crashed as well. There were too many messages like that in the Postgres log:

LOG:  statement: SELECT COUNT(*) FROM tb_voicemail_messages WHERE dir = '/var/spool/asterisk/voicemail/default/1995/INBOX'
LOG:  statement: SELECT COUNT(*) FROM tb_voicemail_messages WHE[the log ends right here]

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

[2007-04-12 13:05:54] WARNING[13226] res_odbc.c: SQL Execute returned an error -1: 53100: Error while executing the query;
ERROR:  could not access status of transaction 0
DETAIL:  could not write to file "pg_subtrans/001C" at offset 147456: No space left on device (175)
[2007-04-12 13:05:54] WARNING[13226] app_voicemail.c: SQL Execute error!
[SELECT COUNT(*) FROM tb_voicemail_messages WHERE dir = '/var/spool/asterisk/voicemail/default/702/INBOX']
Comments:By: Caio Begotti (caio1982) 2007-04-12 11:58:40

I forgot to say that the content in the "Additional Information" box came from /var/log/asterisk/full
By: Clod Patry (junky) 2007-04-12 12:46:51

read the file doc/backtrace.txt and provide required informations.
By: Tilghman Lesher (tilghman) 2007-04-12 13:37:14

Uh, not too many programs out there can run beyond the point where the disk is full.  This isn't really something we can code around.  Allocate more disk!