Summary:ASTERISK-07144: Using ODBC voicemail storage and latest Centos 4.3 updates to mysql server, Asterisk crashed on startup.
Reporter:Edwin horton (edhorton)Labels:
Date Opened:2006-06-10 16:38:58Date Closed:2011-06-07 14:00:44
Versions:Frequency of
Environment:Attachments:( 0) gdb.txt
Description:On a production server, Centos was updated to 2.6.9-34.0.1.ELsmp kernel and latest mysql-server.  Then, Asterisk, Zaptel-1.2.6, Libpri-1.2.3 and Asterisk-addons-1.2.3.  apps/Makefile edited to allow ODBC voicemail storage as was done to Asterisk-1.2.5 before.  Using same config files and database, Asterisk crashes at startup with a "broken pipe" seg fault error.  If asterisk is recompiled without the apps/Makefile change, it functions perfectly except that voicemail storage is file system based as before.  Sill using realtime static to define parameters for voicemail.conf.


Same system performed flawlessly with 1.2.5 and previous centos kernel.  I set up an identical server, completely fresh install, copied config files and database.  Same crash.  There is no indication in debug.  All connections to ODBC are said to be OK.  Also using Realtime for extensions, and static file configs.  ODBCConfig seems happy with connector as well.
Comments:By: Andrey S Pankov (casper) 2006-06-11 17:10:26

If it crashes could you please provide a gdb backtrace for that?

By: Edwin horton (edhorton) 2006-06-12 15:09:42

Set up an identical server, identical MySql database and congig files on a Centos 4.3 system - fresh install.  No updates to Kernel or applications.  Kernel 2.6.9-34.ELsmp in use.  No problem with Asterisk- and ODBC Voicemail.  I noticed the recent update, also loads a new MySQL Server, which was not loaded on my correctly running system.

By: Serge Vecher (serge-v) 2006-06-12 15:14:20

I don't think there is prepare.c in standard Asterisk distribution...

By: Andrey S Pankov (casper) 2006-06-12 16:20:38

vechers: this is because USE_ODBC_STORAGE is defined... and prepare.c seems to
be from libODBC.

By: Serge Vecher (serge-v) 2006-06-19 12:05:27

well, if it's not Asterisk crashing, that I'm not sure if we can do much. Also, for the future, it's helpful to also show 'bt full'

Can you please make sure your logger.conf has the following line:
  console => notice,warning,error,debug

then restart asterisk with the following command "asterisk -vvvvddddc" and post the console capture here as an attachment please. Thanks.

By: Tilghman Lesher (tilghman) 2006-06-19 13:24:33

Also, in gdb:

(gdb) frame 3
(gdb) p sql

By: Tilghman Lesher (tilghman) 2006-06-22 10:10:38

Closing -- appears to be a bug in libmysqlclient.  Nothing to do on this end.