asterisk users - Sep 2009 - Voicemail Crash - ODBC Realtime

Running 1.4.26.2 on CentOS 5.3

Using ODBC with mysql for voicemail storage. Everytime my dialplan tries to open
a connection to save a message or retrieve a stored message, Asterisk dumps out
and restarts with:

Asterisk ended with exit status 127
Asterisk died with code 127.
Automatically restarting Asterisk.
mpg123: no process killed

It restarts fine, but still no voicemail. Nothing in a Mysql query log show
anything of any interest either. Switching back to 'flat file' storage
works fine. Any thoughts?

Thanks.


Bryan Ekelund

STATEMENT OF CONFIDENTIALITY:



The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. If you are not the intended
recipient, please notify WHI Solutions immediately at gc at whisolutions.com,
and destroy all copies of this message and any attachments.

On Monday 21 September 2009 01:46:55 pm Ekelund, Bryan
wrote:
> Running 1.4.26.2 on CentOS 5.3
>
> Using ODBC with mysql for voicemail storage. Everytime my dialplan tries to
> open a connection to save a message or retrieve a stored message, Asterisk
> dumps out and restarts with:
>
> Asterisk ended with exit status 127
> Asterisk died with code 127.
> Automatically restarting Asterisk.
> mpg123: no process killed
>
> It restarts fine, but still no voicemail. Nothing in a Mysql query log show
> anything of any interest either. Switching back to 'flat file'
storage
> works fine. Any thoughts?
Please read doc/backtrace.txt.  You've given just enough information to
verify
that there is a problem, but not enough to diagnose where the problem lies.

-- 
Tilghman