• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Forwarded to devs Occasional "ODBC error #HY000: [ma-3.0.8][10.1.48-MariaDB]Prepared statement needs to be re-prepared" during backups

Bitpalast

Plesk addicted!
Plesk Guru
Username: Peter Debik

TITLE

Occasional "ODBC error #HY000: [ma-3.0.8][10.1.48-MariaDB]Prepared statement needs to be re-prepared" during backups

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 7.9 with latest OS updates
Obsidian, latest MU

PROBLEM DESCRIPTION

Across all of our dedicated servers we occasionally see one or more of these messages in the nightly backup log of full server backups (admin level):

Warning: Domain "domain.tld"
Unable to back up applications. Error: ODBC error #HY000: [ma-3.0.8][10.1.48-MariaDB]Prepared statement needs to be re-prepared

Most often the message only appears exactly once in a backup, sometimes it appears twice or up to five times relating to different domains per message.

STEPS TO REPRODUCE

Cannot be reproduced manually. It appears occasionally, approximately once every 18 full server backups on different machines, e.g. once every 18 weeks on one machine on average. Typical server backup sizes here are 450 GB per machine, approx. 350 subscriptions and 900 domains per machine.

ACTUAL RESULT

Warning: Domain "domain.tld"
Unable to back up applications. Error: ODBC error #HY000: [ma-3.0.8][10.1.48-MariaDB]Prepared statement needs to be re-prepared

EXPECTED RESULT

Backup without SQL error

ANY ADDITIONAL INFORMATION

We'd like to know what the consequence of the behavior is and ideally, how this can be avoided.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
Last edited:
Increasing table_definition_cache and table_open_cache a great deal has solved the issue.
 
Back
Top