[OpenSIPS-Users] db_mysql error, crash
Jeff Pyle
jpyle at fidelityvoice.com
Mon Apr 6 14:58:18 CEST 2009
Correct. Exactly.
On 4/6/09 8:54 AM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:
> You mean at statup, the old problem, right?
>
> Regards,
> Bogdan
>
> Jeff Pyle wrote:
>> Hi Bogdan,
>>
>> I've been following the conversation. I updated on Friday. I haven't seen
>> any more of the prepared statement errors, but I still have the occasional
>> problem connecting to a remote mysqld instance for sip_trace. As before,
>> all network captures and mysqld logs show a successful a connection. Odd.
>>
>>
>> - Jeff
>>
>>
>>
>> On 4/6/09 8:06 AM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:
>>
>>
>>> Hi Jeff,
>>>
>>> There were several fixes in this area (mysql) and I think your case
>>> should be covered. Please update and test again.
>>>
>>> Thanks and regards,
>>> Bogdan
>>>
>>> Jeff Pyle wrote:
>>>
>>>> Hi Bogdan,
>>>>
>>>> Is this information helpful for you? Am I looking at the correct item?
>>>>
>>>> I've had several more crashes since this one, but absolutely no hint as to
>>>> why. No mysql errors on these. Nor core dumps. It seems to happen only
>>>> after the proxy is up for a while. I'm attempting to run it with debug=4
>>>> but it's hard to keep track of that much data. Hopefully I'll catch a
>>>> crash
>>>> at debug=4 to know at least which module is causing it.
>>>>
>>>>
>>>> Thanks,
>>>> Jeff
>>>>
>>>>
>>>>
>>>> On 3/25/09 2:28 PM, "Jeff Pyle" <jpyle at fidelityvoice.com> wrote:
>>>>
>>>>
>>>>
>>>>> Hi Bogdan,
>>>>>
>>>>> CentOS 5.2 running 2.6.18-92.1.22.el5xen.
>>>>>
>>>>> Mysql client lib came from Mysql's own RPM named
>>>>> MySQL-Cluster-gpl-client-6.3.20-0.rhel5. The file itself is called
>>>>> libmysqlclient.so.16.0.0 or libmysqlclient_r.so.16.0.0.
>>>>>
>>>>> Does that answer the version question? I'm not sure how to tell
>>>>> otherwise.
>>>>>
>>>>>
>>>>> - Jeff
>>>>>
>>>>>
>>>>>
>>>>> On 3/25/09 2:22 PM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi Jeff,
>>>>>>
>>>>>> What OS are you using? and what version for mysql client lib?
>>>>>>
>>>>>> Thanks and regards,
>>>>>> Bogdan
>>>>>>
>>>>>> Jeff Pyle wrote:
>>>>>>
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I woke up this morning to this on Opensips 1.5.0:
>>>>>>>
>>>>>>> Mar 25 08:50:10 opensips[12439]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:10 opensips[12439]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:18 opensips[12412]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:18 opensips[12412]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:19 opensips[12439]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:19 opensips[12439]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:23 opensips[12412]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:23 opensips[12412]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:27 opensips[12412]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:27 opensips[12412]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:27 opensips[12439]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:27 opensips[12439]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:30 opensips[12439]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:30 opensips[12439]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:50:54 opensips[12412]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:50:54 opensips[12412]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:51:48 opensips[12439]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:51:48 opensips[12439]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:51:55 opensips[12412]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:51:55 opensips[12412]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:52:16 opensips[12412]:
>>>>>>> ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute()
>>>>>>> failed(2): (1210) Incorrect arguments to mysql_stmt_execute
>>>>>>> Mar 25 08:52:16 opensips[12412]: ERROR:dialog:remove_dialog_from_db:
>>>>>>> failed to delete database information
>>>>>>> Mar 25 08:52:25 opensips[12400]: INFO:core:handle_sigs: child process
>>>>>>> 12435 exited normally, status=1
>>>>>>> Mar 25 08:52:25 opensips[12400]: INFO:core:handle_sigs: terminating
>>>>>>> due to SIGCHLD
>>>>>>> Mar 25 08:52:25 opensips[12412]: INFO:core:sig_usr: signal 15 received
>>>>>>> Mar 25 08:52:25 opensips[12468]: INFO:core:sig_usr: signal 15 received
>>>>>>> Mar 25 08:52:25 opensips[12437]: INFO:core:sig_usr: signal 15 received
>>>>>>>
>>>>>>> I have all the memory debug output from the crash as well (several
>>>>>>> hundred lines). Unfortunately no core was generated even with Œulimit
>>>>>>> c 0¹ and a working directory set.
>>>>>>>
>>>>>>>
>>>>>>> - Jeff
>>>>>>>
>>>>>>>
>>>>
>>>>
>>
>>
>>
>
More information about the Users
mailing list