Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-918

non-root gluster install failed to startup - directory permission issues

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.1.0
    • 1.1.0
    • ?
    • amazon with gluster installed
    • 2017-18

    Description

      installed a 2 pm system with gluster storage and it failed to startup

      Issued here is that data1 and gluster directory both have root user..
      So Ben needs to look into that one a bit more..

      Sep 13 00:18:33 ip-172-30-0-161 ProcessMonitor[3531]: 33.282149 |0|0|0| E 18 CAL0000: ERROR: Failed test write to DBRoot: /home/mariadb-user/mariadb/columnstore/data1

      [mariadb-user@ip-172-30-0-161 columnstore]$ ll
      total 32
      drwxr-xr-x 2 mariadb-user mariadb-user 4096 Sep 13 00:05 bin
      drwxrwxr-x 3 mariadb-user mariadb-user 17 Sep 13 00:04 data
      drwxr-xr-x 3 root root 4096 Sep 13 00:08 data1
      drwxr-xr-x 2 mariadb-user mariadb-user 6 Sep 13 00:06 data2
      drwxr-xr-t 2 mariadb-user mariadb-user 4096 Sep 13 03:29 etc
      drwxr-xr-x 4 root root 32 Sep 13 00:08 gluster
      drwxr-xr-x 2 mariadb-user mariadb-user 8192 Sep 13 00:05 lib
      drwxr-xr-x 3 mariadb-user mariadb-user 29 Sep 13 00:05 local
      drwxr-xr-x 11 mariadb-user mariadb-user 4096 Sep 13 00:07 mysql
      drwxr-xr-x 2 mariadb-user mariadb-user 94 Sep 11 18:42 post
      rw-rr- 1 mariadb-user mariadb-user 24 Sep 11 18:33 releasenum

      Attachments

        Issue Links

          Activity

            People

              dleeyh Daniel Lee (Inactive)
              hill David Hill (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.