what about the permissions of the actual host directory you are exporting?

On Wed, Jul 27, 2016 at 9:11 AM, Den Cowboy <[email protected]> wrote:

> Yeah, that's something which is different. On my master I was working with
> exportfs -a etc.
> But now it doesn't matter. The permissions are IP based. (we hadded the
> range in which are cluster is running)
>
> *[*3:09*]*
> <https://evolane.slack.com/archives/D11S07596/p1469624980000255>
>
>
> ------------------------------
> From: [email protected]
> Date: Wed, 27 Jul 2016 09:04:12 -0400
> Subject: Re: Persistent Storage MYSQL
> To: [email protected]
> CC: [email protected]
>
>
> what are the permissions of the NFS exported volume?  and what is in the
> export definition?
>
>
> On Wed, Jul 27, 2016 at 8:35 AM, Den Cowboy <[email protected]> wrote:
>
> I try to make my MySQL pod persistent.
> I always did this on training-environmnents where my DNS-server was on my
> master and I had never issues.
> Now my NFS is on another server.
>
> My pv looks like this
> {
>   "apiVersion": "v1",
>   "kind": "PersistentVolume",
>   "metadata": {
>     "name": "mysql-data"
>   },
>   "spec": {
>     "capacity": {
>         "storage": "20Gi"
>         },
>     "accessModes": [ "ReadWriteMany" ],
>     "nfs": {
>         "path": "/path/mysql",
>         "server": "server-IP"
>     }
>   }
> }
>
> I also created a pvc and edited the dc of my mysql to use it. Just like I
> always did on my training environment.
> After editting the dc there is a new deploy triggered but my pod is going
> in a recreation loop.
>
>
> 2016-07-27 08:17:01 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld
> (mysqld 5.6.26) starting as process 18 ...
> 2016-07-27 08:17:01 18 [Warning] Can't create test file
> /var/lib/mysql/data/mysql-2-edp7q.lower-test
> 2016-07-27 08:17:01 18 [Warning] Can't create test file
> /var/lib/mysql/data/mysql-2-edp7q.lower-test
> *[*10:17*]*
> <https://evolane.slack.com/archives/D11S07596/p1469607466000068>
> 2016-07-27 08:17:01 7fd2befc3840  InnoDB: Operating system error number 13
> in a file operation.
> InnoDB: The error means mysqld does not have the access rights to
> InnoDB: the directory.
> 2016-07-27 08:17:01 18 [ERROR] InnoDB: Creating or opening ./ibdata1
> failed!
>
> Does someone know what could be the issue?
> When I create a directory /mnt on my node-host of OS I'm able to mount to
> my NFS storage server. So why isn't this working for my mysql container?
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>
>
> --
> Ben Parees | OpenShift
>
>


-- 
Ben Parees | OpenShift
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to