• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Unknown table engine 'InnoDB' and Requested resource broker

nocrash

Basic Pleskian
---------------------------------------------------------------
PRODUCT, VERSION, MICROUPDATE, OPERATING SYSTEM, ARCHITECTURE

10.4.4 SuSE 11.4 1013111102.18 (patch version="45"), 64 bit

PROBLEM DESCRIPTION

Something strange with the mysql database?

STEPS TO REPRODUCE

/etc/init.d/psa stop

/etc/init.d/psa start

ACTUAL RESULT

First
$ /etc/init.d/psa start
Starting psa... done
Starting xinetd service... done
Starting named service... done
Starting mysql service... done
Starting postgresql service... not installed
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... done
ERROR 1286 (42000) at line 1: Unknown table engine 'InnoDB'
ERROR 1286 (42000) at line 1: Unknown table engine 'InnoDB'
Starting psa... done
ERROR 1286 (42000) at line 1: Unknown table engine 'InnoDB'

I read about this error at 264208 and did a mysqlcheck -Aca --auto-repair -uadmin -p`cat /etc/psa/.psa.shadow`

Now the result was at first start..
$ /etc/init.d/psa start
Starting psa... done
Starting xinetd service... done
Starting named service... done
Starting mysql service... done
Starting postgresql service... not installed
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
2012-10-29T13:55:16+01:00 DEBUG (7): Requested resource broker for 'aps.environment' in context ID 'hosting-44-https'
2012-10-29T13:55:16+01:00 DEBUG (7): Requested existing resource, ID: 73e26a59-fb8d-4fe4-9815-a17add8fb4f4
2012-10-29T13:55:16+01:00 DEBUG (7): Apspp_Hosting_Resource_Environment_Site::load
2012-10-29T13:55:16+01:00 DEBUG (7): Requested resource broker for 'aps.database' in context ID 'hosting-44-https'
2012-10-29T13:55:16+01:00 DEBUG (7): Requested existing resource, ID: ced38058-7381-434a-98f8-e0224eddfa4e
2012-10-29T13:55:16+01:00 DEBUG (7): Apspp_Hosting_Resource_Environment_Site::urlMapping
2012-10-29T13:55:16+01:00 DEBUG (7): Apspp_Hosting_Resource_Environment_Site::urlMapping
2012-10-29T13:55:21+01:00 DEBUG (7): Requested resource broker for 'aps.environment' in context ID 'hosting-501-https'
[..]
2012-10-29T13:56:24+01:00 DEBUG (7): Apspp_Hosting_Resource_Environment_Site::urlMapping
2012-10-29T13:56:24+01:00 DEBUG (7): Apspp_Hosting_Resource_Environment_Site::urlMapping
2012-10-29T13:56:24+01:00 DEBUG (7): Apspp_Hosting_Resource_Environment_Site::urlMapping
Starting psa... done
Starting drwebd service... failed

what does this mean? should i care of something? following restarts of psa are OK !


EXPECTED RESULT


ANY ADDITIONAL INFORMATION


--------------------------------------------------------------
 
Back
Top