Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.2
-
None
Description
Build tested: 5.5.2-1 (Jenkin #1560)
When installing DEB packages on Debian and Ubuntu OSs, the follow errors appeared complaining ColumnStore engine does not exist. But it continued to setup ColumnStore system catalog. Installation did continue and the stack did function correctly.
s2pm1: Setting up mariadb-plugin-columnstore (1:10.5.9.6-5.5.2+maria~bionic) ...
s2pm1: dpkg: mariadb-plugin-columnstore: dependency problems, but configuring anyway as you requested:
s2pm1: mariadb-plugin-columnstore depends on mariadb-server-10.5 (= 1:10.5.9.6+maria~bionic).
s2pm1:
s2pm1: Configuration file '/etc/columnstore/Columnstore.xml', does not exist on system.
s2pm1: Installing new config file as you requested.
s2pm1:
s2pm1: Configuration file '/etc/columnstore/ErrorMessage.txt', does not exist on system.
s2pm1: Installing new config file as you requested.
s2pm1:
s2pm1: Configuration file '/etc/columnstore/MessageFile.txt', does not exist on system.
s2pm1: Installing new config file as you requested.
s2pm1:
s2pm1: Configuration file '/etc/columnstore/storagemanager.cnf', does not exist on system.
s2pm1: Installing new config file as you requested.
s2pm1:
s2pm1: Configuration file '/etc/mysql/mariadb.conf.d/columnstore.cnf', does not exist on system.
s2pm1: Installing new config file as you requested.
s2pm1: Job for mariadb.service failed because the control process exited with error code.
s2pm1: See "systemctl status mariadb.service" and "journalctl -xe" for details.
s2pm1: checking for engine columnstore...
s2pm1: columnstore doesn't exist
s2pm1: There was an error installing MariaDB ColumnStore engine plugin. Continue to install the engine though. \
s2pm1: Please resolve the issues and run necessary scripts manually.
s2pm1: Populating the engine initial system catalog.
[ubuntu18:root~]# systemctl status mariadb.service
● mariadb.service - MariaDB 10.5.9-6 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 Thu 2021-03-04 20:43:17 UTC; 21min ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 8434 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Process: 8432 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 8324 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`;
Process: 8322 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 8321 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 8413 (mariadbd)
Status: "Taking your SQL requests now..."
Tasks: 9 (limit: 4915)
CGroup: /system.slice/mariadb.service
└─8413 /usr/sbin/mariadbd
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: infinidb_querystats.user_priority OK
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: information_schema
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: mytest
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: mytest.lineitem OK
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: mytest.orders OK
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: mytest.quicktest OK
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: performance_schema
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: test
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: Phase 7/7: Running 'FLUSH PRIVILEGES'
Mar 04 20:43:20 vagrant /etc/mysql/debian-start[8441]: OK
[ubuntu18:root~]# journalctl -xe
–
– The start-up result is RESULT.
Mar 04 20:58:36 vagrant sshd[9386]: Received disconnect from 10.0.2.2 port 43884:11: disconnected by user
Mar 04 20:58:36 vagrant sshd[9386]: Disconnected from user root 10.0.2.2 port 43884
Mar 04 20:58:36 vagrant sshd[9386]: pam_unix(sshd:session): session closed for user root
Mar 04 20:58:36 vagrant systemd-logind[404]: Removed session 15.
– Subject: Session 15 has been terminated
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
– Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
–
– A session with the ID 15 has been terminated.
Mar 04 21:03:43 vagrant ntpd[453]: receive: Unexpected origin timestamp 0xe3ebc9b1.2a5f4389 does not match aorg 0000000000.00000000 fr
Mar 04 21:04:41 vagrant sshd[9676]: Accepted password for root from 10.0.2.2 port 43886 ssh2
Mar 04 21:04:41 vagrant sshd[9676]: pam_unix(sshd:session): session opened for user root by (uid=0)
Mar 04 21:04:41 vagrant systemd-logind[404]: New session 16 of user root.
– Subject: A new session 16 has been created for user root
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
– Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
–
– A new session with the ID 16 has been created for the user root.
–
– The leading process of the session is 9676.
Mar 04 21:04:41 vagrant systemd[1]: Started Session 16 of user root.
– Subject: Unit session-16.scope has finished start-up
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
– Unit session-16.scope has finished starting up.
–
– The start-up result is RESULT.