Re: Help for "error loading key" '143'

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Mon, 19 Nov 2012 13:32:38 -0800 (PST)

On Mon, 19 Nov 2012, Simone Caruso wrote:
> 4451 snprintf(query, sizeof query,
> (gdb)
> 4456 dsn->dsn_filter == NULL ? "" : " AND ",
> (gdb)
> 4451 snprintf(query, sizeof query,
> (gdb)

Odd, why'd it step backwards?

A "print query" here might be helpful.

> 4459 err = odbx_query(odbx, query, 0);
> (gdb)
> [New Thread 0x7f9a73d61700 (LWP 26751)]
> 4460 if (err < 0)
> (gdb)
> 4464 db->db_status = err;

The patch I just sent you will (should, at least) cause the text matching
this error code to be logged.

> (gdb)
> 4466 if (reconnected)
> (gdb)
> 4478 status = odbx_error_type(odbx, err);
> (gdb)
> [New Thread 0x7f9a73560700 (LWP 26752)]
> 4493 if (status < 0)
> (gdb) p status
> $1 = 1
> (gdb) n
> 4512 if (db->db_lock != NULL)
> (gdb)
> 4513 (void)
> pthread_mutex_unlock(db->db_lock);
> (gdb)
> [New Thread 0x7f9a72d5f700 (LWP 26753)]
> [Thread 0x7f9a75d65700 (LWP 26733) exited]
> [New Thread 0x7f9a7255e700 (LWP 26755)]
> 4514 return err;
> (gdb)
> 5530 }

So odbx_query() is returning an error. Could be the query is malformed,
could be some I/O problem between the filter and MySQL. Digging in that
area is next.

-MSK
Received on Mon Nov 19 2012 - 21:32:54 PST