Valentin Aitken created BROOKLYN-418:
----------------------------------------
Summary: MariaDB does not install correctly
Key: BROOKLYN-418
URL: https://issues.apache.org/jira/browse/BROOKLYN-418
Project: Brooklyn
Issue Type: Bug
Affects Versions: 0.10.0
Reporter: Valentin Aitken
*Steps to reproduce:*
Deploy {{org.apache.brooklyn.entity.database.mariadb.MariaDbNode}} on
{{aws-ec2:sa-east-1/ami-26b93b4a}}
*Observed behavior:*
Check running says blueprint is on fire.
Contents of
{{/home/users/<User>/brooklyn-managed-processes/apps/<AppId>/entities/MariaDbNode_<EntityId>/console.log}}
prints errors with MariaDb data files.
{noformat}
161220 8:17:41 InnoDB: The InnoDB memory heap is disabled
161220 8:17:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161220 8:17:41 InnoDB: Compressed tables use zlib 1.2.3
161220 8:17:41 InnoDB: Using Linux native AIO
161220 8:17:41 InnoDB: Initializing buffer pool, size = 128.0M
161220 8:17:41 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
{noformat}
*Analysis:*
On {{customize}} phase {{MariaDbNode}} performs launch in order to configure
the database and then it invokes stop.
The reason for having errors when accessing ./ibdata1 is probably because of
the eager stopping performed on stop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
