All,
- We recently deployed a new environment for a client running Piwik. (used a Bitnami instance on AWS).
- After the update of Piwik to v 1.12 everything went
- But after an apt-get update apt-get upgrade the Mysql server is not able to start.
- Any thoughts?
Following is the logfile of /opt/bitnami/mysql/data
130619 09:05:31 mysqld_safe Starting mysqld.bin daemon with databases from /opt/bitnami/mysql/data
130619 9:05:31 [Warning] The syntax ‘–log-slow-queries’ is deprecated and will be removed in a future release. Please use ‘–slow-query-log’/’–slow-query-log-file’ instead.
130619 9:05:31 [Note] Plugin ‘FEDERATED’ is disabled.
/opt/bitnami/mysql/bin/mysqld.bin: Table ‘plugin’ is read only
130619 9:05:31 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.
130619 9:05:31 InnoDB: The InnoDB memory heap is disabled
130619 9:05:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130619 9:05:31 InnoDB: Compressed tables use zlib 1.2.3
130619 9:05:31 InnoDB: Using Linux native AIO
/opt/bitnami/mysql/bin/mysqld.bin: Can’t create/write to file ‘/opt/bitnami/mysql/tmp/ibeks816’ (Errcode: 13)
130619 9:05:31 InnoDB: Error: unable to create temporary file; errno: 13
130619 9:05:31 [ERROR] Plugin ‘InnoDB’ init function returned error.
130619 9:05:31 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
/opt/bitnami/mysql/bin/mysqld.bin: File ‘/opt/bitnami/mysql/data/ip-10-33-192-194-slow.log’ not found (Errcode: 13)
130619 9:05:31 [ERROR] Could not use /opt/bitnami/mysql/data/ip-10-33-192-194-slow.log for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQ
L server and restart it.
130619 9:05:31 [ERROR] Unknown/unsupported storage engine: InnoDB
130619 9:05:31 [ERROR] Aborting
130619 9:05:31 [Note] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete
130619 09:05:31 mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/mysqld.pid ended