| Summary: | ASTERISK-08946: cdr_odbc causes segfault when odbc database becomes unavailable | ||
| Reporter: | jmls (jmls) | Labels: | |
| Date Opened: | 2007-03-06 09:53:29.000-0600 | Date Closed: | 2007-03-19 19:21:03 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | CDR/cdr_odbc |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | using cdr_odbc, if the database goes away (for whatever reason) asterisk will segfault soon afterwards. bt full will be attached soon ... | ||
| Comments: | By: Leif Madsen (lmadsen) 2007-03-06 10:18:42.000-0600 I think this is the same thing I'm seeing on my other bugs that I have open. I'm going to create relationships to them... and now I realize it's all probably the same fundamental issue underneath them, so the multiple bugs I have open I'm sure are really all duplicates of each other. The issue seems to be that Asterisk segfaults if either the database goes away, or if the SQL statement that is being executed is invalid, (e.g. SELECT <something> FROM <non_existant_table>). An ERROR or WARNING should be returned, but not a segfault :) I can reliably reproduce this, so if you want a different core from what I've got in the related bugs, then let me know and I'll post it. By: Leif Madsen (lmadsen) 2007-03-06 10:19:40.000-0600 Also of note is that I'm no longer using pgcluster, but rather just a standalone PostgreSQL server on CentOS 4.4 By: Leif Madsen (lmadsen) 2007-03-19 19:21:03 Until I can reproduce this, or someone else runs into the same issue, I'm going to consider this closed. jmls: I think you said you weren't getting this anymore -- reopen if needed! | ||