ERROR 2014-05-14 20:35:57.000000 [ 1 ] mysql_stmt_execute failed: Unknown prepared statement handler (1) given to mysqld_stmt_execute (1243 1243) -> libgearman-server/plugins/queue/mysql/queue.cc:432
errors when a worker reports the completion of a job after the MySQL server connection is dropped and re-connected automatically. The first error code in the parentheses is from mysql_errno(queue->con) and the second from mysql_stmt_errno(queue->done_stmt).
There may be some sensitivity in this issue that the first thing that happens after a re-connection to the MySQL server be the worker completion of a job as opposed to the addition of a new job from a client.
I have been able to recreate this in testing whereby I can get the job server to log either:
ERROR 2014-05-14 20:34:05.000000 [ 1 ] mysql_stmt_execute failed: Incorrect arguments to mysqld_stmt_execute (1210 1210) -> libgearman- server/ plugins/ queue/mysql/ queue.cc: 432
or:
ERROR 2014-05-14 20:35:57.000000 [ 1 ] mysql_stmt_execute failed: Unknown prepared statement handler (1) given to mysqld_stmt_execute (1243 1243) -> libgearman- server/ plugins/ queue/mysql/ queue.cc: 432
errors when a worker reports the completion of a job after the MySQL server connection is dropped and re-connected automatically. The first error code in the parentheses is from mysql_errno( queue-> con) and the second from mysql_stmt_ errno(queue- >done_stmt) .
There may be some sensitivity in this issue that the first thing that happens after a re-connection to the MySQL server be the worker completion of a job as opposed to the addition of a new job from a client.