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

mcs-start-storagemanager.py[9135]: S3 storage has not been set up for MariaDB ColumnStore. StorageManager service fails to start

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • Icebox
    • Storage Manager
    • None
    • CentOS 7.8, MariaDB Community Server + Single Node Columnstore

    Description

      I have installed mariadb and columnstore on the server according to the instructions page https://mariadb.com/docs/deploy/community-single-columnstore-cs105-centos7/. I want to use the local storage of columnstore, so I left the configuration file storagemanager.cnf unchanged.

      Now when I start columnstore with systemctl start mariadb-columnstore I get the following error message:

      [root@hz5serv columnstore]# systemctl -l status mariadb-columnstore
      ● mariadb-columnstore.service - mariadb-columnstore
         Loaded: loaded (/usr/lib/systemd/system/mariadb-columnstore.service; enabled; vendor preset: disabled)
         Active: active (exited) since Di 2020-07-28 10:40:30 CEST; 1h 41min ago
        Process: 9092 ExecStop=/usr/bin/mariadb-columnstore-stop.sh (code=exited, status=0/SUCCESS)
        Process: 9133 ExecStart=/usr/bin/mariadb-columnstore-start.sh (code=exited, status=0/SUCCESS)
       Main PID: 9133 (code=exited, status=0/SUCCESS)
         CGroup: /system.slice/mariadb-columnstore.service
       
      Jul 28 10:40:26 hz5serv.heinze.de systemd[1]: Starting mariadb-columnstore...
      Jul 28 10:40:26 hz5serv.heinze.de mariadb-columnstore-start.sh[9133]: Job for mcs-storagemanager.service failed because the control process exited with error code. See "systemctl status mcs-storagemanager.service" and "journalctl -xe" for details.
      Jul 28 10:40:30 hz5serv.heinze.de systemd[1]: Started mariadb-columnstore.
      [root@hz5serv columnstore]# systemctl -l status mcs-storagemanager
      ● mcs-storagemanager.service - storagemanager
         Loaded: loaded (/usr/lib/systemd/system/mcs-storagemanager.service; disabled; vendor preset: disabled)
         Active: failed (Result: exit-code) since Di 2020-07-28 10:40:26 CEST; 1h 41min ago
        Process: 9135 ExecStartPre=/usr/bin/mcs-start-storagemanager.py (code=exited, status=1/FAILURE)
       
      Jul 28 10:40:26 hz5serv.heinze.de systemd[1]: Starting storagemanager...
      Jul 28 10:40:26 hz5serv.heinze.de mcs-start-storagemanager.py[9135]: S3 storage has not been set up for MariaDB ColumnStore. StorageManager service fails to start.
      Jul 28 10:40:26 hz5serv.heinze.de systemd[1]: mcs-storagemanager.service: control process exited, code=exited status=1
      Jul 28 10:40:26 hz5serv.heinze.de systemd[1]: Failed to start storagemanager.
      Jul 28 10:40:26 hz5serv.heinze.de systemd[1]: Unit mcs-storagemanager.service entered failed state.
      Jul 28 10:40:26 hz5serv.heinze.de systemd[1]: mcs-storagemanager.service failed.
      

      On the https://mariadb.com/kb/en/system-troubleshooting-mariadb-columnstore/ page, in the section "startSystem problems and how to diagnose" it says that I should run the command mcsadmin getsystemi to get detailed error information. However, the mcsadmin command is unknown on the server.
      In the previous section, it says to run the script ./usr/local/mariadb/columnstore/bin/aliasColumnstore to create an alias mcsadmin. Unfortunately the file does not exist around my server. Already the directory /usr/local/mariadb does not exist. Only under /usr/share there is a directory columnstore on my server.

      What can I do so that columnstore runs without errors?
      Can I still start my tests for columnstore?

      Attachments

        Activity

          People

            Unassigned Unassigned
            KB_Heinze Karsten Budde
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.