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

Columnstore issues while upgrading server from 10.6 to 11.4

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • 2025-9

    Description

      https://mdbe-buildbot.mariadb.net/#/builders/10/builds/59307

      Warning: The unit file, source configuration file or drop-ins of mariadb.service changed on disk. Run 'systemctl daemon-reload' to reload units.
      renamed '/etc/logrotate.d/mysql-server' -> '/etc/logrotate.d/mysql-server.dpkg-bak'
      Setting up mariadb-plugin-cracklib-password-check (1:11.4.8.5+maria~ubu2204) ...
      Setting up mariadb-plugin-gssapi-client (1:11.4.8.5+maria~ubu2204) ...
      Setting up mariadb-plugin-rocksdb (1:11.4.8.5+maria~ubu2204) ...
      Setting up mariadb-plugin-columnstore (1:11.4.8.5-23.10.6+maria~ubu2204) ...
      There were authentication issues running install_mcs_mysql.sh script. The log is available in /var/log/mariadb/columnstore/install/mysql_install.log. Please re-run columnstore-post-install manually after solving the authentication issues.
      There was an error installing MariaDB ColumnStore engine plugin. Continue to install the engine though. Please resolve the issues and run necessary scripts manually.
      At least one file is not owned by mysql in /var/lib/columnstore. Running chown...
      Populating the engine initial system catalog.
      Failed to start mariadb-columnstore.service: Unit mariadb-columnstore.service is masked.
      Setting up mariadb-plugin-gssapi-server (1:11.4.8.5+maria~ubu2204) ...
      Setting up mariadb-server-compat (1:11.4.8.5+maria~ubu2204) ...
      Setting up mariadb-plugin-s3 (1:11.4.8.5+maria~ubu2204) ...
      Processing triggers for man-db (2.10.2-1) ...
      Processing triggers for libc-bin (2.35-0ubuntu3.10) ...
      NEEDRESTART-VER: 3.5
      NEEDRESTART-KCUR: 6.8.0-1036-gcp
      NEEDRESTART-KEXP: 6.8.0-1036-gcp
      NEEDRESTART-KSTA: 1
      W: --force-yes is deprecated, use one of the options starting with --allow instead.
      Starting server
      ● mariadb.service - MariaDB 11.4.8-5 database server
           Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
          Drop-In: /etc/systemd/system/mariadb.service.d
                   └─migrated-from-my.cnf-settings.conf
           Active: active (running) since Wed 2025-09-10 14:32:45 CEST; 4s ago
             Docs: man:mariadbd(8)
                   https://mariadb.com/kb/en/library/systemd/
          Process: 31962 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
          Process: 31963 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
          Process: 31965 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
          Process: 32100 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
          Process: 32102 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
         Main PID: 32051 (mariadbd)
           Status: "Taking your SQL requests now..."
            Tasks: 21 (limit: 126588)
           Memory: 86.1M
              CPU: 1.482s
           CGroup: /system.slice/mariadb.service
                   └─32051 /usr/sbin/mariadbd
      

      Attachments

        Activity

          People

            tturenko Timofey Turenko
            tturenko Timofey Turenko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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