[
https://issues.apache.org/jira/browse/AIRAVATA-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899556#comment-15899556
]
Marcus Christie edited comment on AIRAVATA-2335 at 4/3/17 8:29 PM:
-------------------------------------------------------------------
The Sharing Registry requires MariaDB >= 10.0.5 for FULLTEXT indexing on InnoDB
tables. To be able to install this version of MariaDB I needed to add the
MariaDB yum repo for CentOS 7. I'm included that in the Ansible scripts.
So now MariaDB 10.0.29 is installed but there is a SELinux bug with it. See
https://www.rootusers.com/how-to-fix-mariadb-10-0-29-selinux-update-failure/
and https://jira.mariadb.org/browse/MDEV-11789. I fixed it by running
{noformat}
sudo yum install setroubleshoot-server
sudo ausearch -c 'mysqld_safe_hel' --raw | sudo audit2allow -M my-mysqldsafehel
sudo semodule -i my-mysqldsafehel.pp
sudo service mysql restart
{noformat}
And I had to go through the ausearch/semodule -i steps twice, I believe, once
for granting setgid and once for granting setuid.
I haven't included these steps in the Ansible script yet since this bug is
fixed and shouldn't be a problem in the next release 10.0.30. But if it causes
more problems perhaps it would be good to have it in the Ansible script.
----
10.0.30 was released on 2017-03-08:
https://downloads.mariadb.org/mariadb/+releases/
----
Unfortunately this is still an issue with 10.0.30:
https://jira.mariadb.org/browse/MDEV-12231
Eric is working on a workaround for now, to install the SELinux policy needed
to get the server running until we can upgrade to 10.0.31 which should have the
fix.
was (Author: marcuschristie):
The Sharing Registry requires MariaDB >= 10.0.5 for FULLTEXT indexing on InnoDB
tables. To be able to install this version of MariaDB I needed to add the
MariaDB yum repo for CentOS 7. I'm included that in the Ansible scripts.
So now MariaDB 10.0.29 is installed but there is a SELinux bug with it. See
https://www.rootusers.com/how-to-fix-mariadb-10-0-29-selinux-update-failure/
and https://jira.mariadb.org/browse/MDEV-11789. I fixed it by running
{noformat}
sudo yum install setroubleshoot-server
sudo ausearch -c 'mysqld_safe_hel' --raw | sudo audit2allow -M my-mysqldsafehel
sudo semodule -i my-mysqldsafehel.pp
sudo service mysql restart
{noformat}
And I had to go through the ausearch/semodule -i steps twice, I believe, once
for granting setgid and once for granting setuid.
I haven't included these steps in the Ansible script yet since this bug is
fixed and shouldn't be a problem in the next release 10.0.30. But if it causes
more problems perhaps it would be good to have it in the Ansible script.
----
10.0.30 was released on 2017-03-08:
https://downloads.mariadb.org/mariadb/+releases/
> Deploy 0.17-SNAPSHOT on Jetstream for testing
> ---------------------------------------------
>
> Key: AIRAVATA-2335
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2335
> Project: Airavata
> Issue Type: Task
> Reporter: Marcus Christie
> Assignee: Marcus Christie
>
> Use Ansible to deploy Airavata version 0.17-SNAPSHOT for testing before 0.17
> is released.
> Notes:
> * Airavata is deployed on 149.165.168.5
> * Seagrid PGA is deployed on http://149.165.156.11/
> * Scigap PGA is deployed on http://149.165.156.52/
> * Testdrive PGA is deployed on http://149.165.156.148/
> * DB is deployed on 149.165.172.163
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
