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

/var/log/mariadb/columnstore ownership set to 777 recursive

Details

    • Task
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 1.2.1
    • 1.2.2
    • None
    • None
    • 2018-20

    Description

      In syslogSetup.sh:

      chmod 777 -R /var/log/mariadb/columnstore
      

      That is definitely the wrong thing to do.

      Attachments

        Issue Links

          Activity

            How to test and see the difference between 1.2.1 and 1.2.2.

            on centos 7 as non-root user, do the following:

            install 1.2.1 centos 7 binary package as non-root user and run the following as root user.
            You will see that all the directories is set to 777 permissions, which is what the BUG is about

            rm -rf /var/log/mariadb/
            /home/mysql/mariadb/columnstore/bin/syslogSetup.sh install --user=mysql
            ll /var/log/mariadb/columnstore/
            total 8
            drwxrwxrwx 2 root root 6 Nov 29 22:41 archive
            drwxrwxrwx 2 root root 6 Nov 29 22:41 corefiles
            drwxrwxrwx 2 root root 6 Nov 29 22:41 trace

            install 1.2.2 centos 7 binary package as non-root user and run the following.
            The directories are now 750, which is more secure. 777 is wide open to all.
            You will also notice that the debug/info logs are created with
            "MariaDB Columnstore Installed". That wasnt in 1.2.1.

            rm -rf /var/log/mariadb/
            /home/mysql/mariadb/columnstore/bin/syslogSetup.sh install --user=mysql
            ll /var/log/mariadb/columnstore/
            drwxr-x--- 2 root root 6 Nov 29 22:46 archive
            drwxr-x--- 2 root root 6 Nov 29 22:46 corefiles
            rw------ 1 syslog adm 124 Nov 29 22:46 debug.log
            rw------ 1 syslog adm 124 Nov 29 22:46 info.log
            drwxr-x--- 2 root root 6 Nov 29 22:46 trace

            hill David Hill (Inactive) added a comment - How to test and see the difference between 1.2.1 and 1.2.2. on centos 7 as non-root user, do the following: install 1.2.1 centos 7 binary package as non-root user and run the following as root user. You will see that all the directories is set to 777 permissions, which is what the BUG is about rm -rf /var/log/mariadb/ /home/mysql/mariadb/columnstore/bin/syslogSetup.sh install --user=mysql ll /var/log/mariadb/columnstore/ total 8 drwxrwxrwx 2 root root 6 Nov 29 22:41 archive drwxrwxrwx 2 root root 6 Nov 29 22:41 corefiles drwxrwxrwx 2 root root 6 Nov 29 22:41 trace install 1.2.2 centos 7 binary package as non-root user and run the following. The directories are now 750, which is more secure. 777 is wide open to all. You will also notice that the debug/info logs are created with "MariaDB Columnstore Installed". That wasnt in 1.2.1. rm -rf /var/log/mariadb/ /home/mysql/mariadb/columnstore/bin/syslogSetup.sh install --user=mysql ll /var/log/mariadb/columnstore/ drwxr-x--- 2 root root 6 Nov 29 22:46 archive drwxr-x--- 2 root root 6 Nov 29 22:46 corefiles rw ------ 1 syslog adm 124 Nov 29 22:46 debug.log rw ------ 1 syslog adm 124 Nov 29 22:46 info.log drwxr-x--- 2 root root 6 Nov 29 22:46 trace

            Build tested: 1.2.2-1

            Installed 1.2.2-1 as non-root (guest user) on centos 7. I got errors when running the command under the root user:

            [root@localhost ~]# export COLUMNSTORE_INSTALL_DIR=/home/guest/mariadb/columnstore
            [root@localhost ~]# export LD_LIBRARY_PATH=:/home/guest/mariadb/columnstore/lib:/home/guest/mariadb/columnstore/mysql/lib:/home/guest/mariadb/columnstore/lib:/home/guest/mariadb/columnstore/mysql/lib
            [root@localhost ~]#
            [root@localhost ~]# /home/guest/mariadb/columnstore/bin/syslogSetup.sh install --user=guest
            /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 66: /usr/local/mariadb/columnstore/bin/getConfig: No such file or directory

            System logging being used: rsyslog

            cp: cannot stat ‘/usr/local/mariadb/columnstore/bin/columnstoreSyslog7’: No such file or directory
            sed: can't read /etc/rsyslog.d/49-columnstore.conf: No such file or directory
            sed: can't read /etc/rsyslog.d/49-columnstore.conf: No such file or directory
            chmod: cannot access ‘/etc/rsyslog.d/49-columnstore.conf’: No such file or directory
            chmod: cannot access ‘/etc/logrotate.d/columnstore’: No such file or directory
            /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory
            /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory
            /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory
            /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory

            dleeyh Daniel Lee (Inactive) added a comment - Build tested: 1.2.2-1 Installed 1.2.2-1 as non-root (guest user) on centos 7. I got errors when running the command under the root user: [root@localhost ~] # export COLUMNSTORE_INSTALL_DIR=/home/guest/mariadb/columnstore [root@localhost ~] # export LD_LIBRARY_PATH=:/home/guest/mariadb/columnstore/lib:/home/guest/mariadb/columnstore/mysql/lib:/home/guest/mariadb/columnstore/lib:/home/guest/mariadb/columnstore/mysql/lib [root@localhost ~] # [root@localhost ~] # /home/guest/mariadb/columnstore/bin/syslogSetup.sh install --user=guest /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 66: /usr/local/mariadb/columnstore/bin/getConfig: No such file or directory System logging being used: rsyslog cp: cannot stat ‘/usr/local/mariadb/columnstore/bin/columnstoreSyslog7’: No such file or directory sed: can't read /etc/rsyslog.d/49-columnstore.conf: No such file or directory sed: can't read /etc/rsyslog.d/49-columnstore.conf: No such file or directory chmod: cannot access ‘/etc/rsyslog.d/49-columnstore.conf’: No such file or directory chmod: cannot access ‘/etc/logrotate.d/columnstore’: No such file or directory /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory /home/guest/mariadb/columnstore/bin/syslogSetup.sh: line 245: /usr/local/mariadb/columnstore/bin/cplogger: No such file or directory

            unknown why its failing. i tested as mysql user, will restest as guest user to see if i can reproduce

            hill David Hill (Inactive) added a comment - unknown why its failing. i tested as mysql user, will restest as guest user to see if i can reproduce

            worked for me on ubuntu18 using the commands output by post-install:
            /home/mysql/mariadb/columnstore/bin/syslogSetup.sh --installdir=/home/mysql/mariadb/columnstore --user=mysql install

            --installdir is required.

            dthompson David Thompson (Inactive) added a comment - worked for me on ubuntu18 using the commands output by post-install: /home/mysql/mariadb/columnstore/bin/syslogSetup.sh --installdir=/home/mysql/mariadb/columnstore --user=mysql install --installdir is required.

            Retested

            dleeyh Daniel Lee (Inactive) added a comment - Retested

            People

              dleeyh Daniel Lee (Inactive)
              LinuxJedi Andrew Hutchings (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.