[MCOL-2227] Cannot create new table Created: 2019-03-11  Updated: 2023-07-20  Resolved: 2023-07-20

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: 1.2.2
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Petr Procházka Assignee: Leonid Fedorov
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

openSUSE 42.3 on VMware
Linux server-musp-bi 4.4.175-89-default #1 SMP Thu Feb 21 16:05:09 UTC 2019 (585633c) x86_64 x86_64 x86_64 GNU/Linux

Attachments: File columnstore.tar.gz     File columnstoreSupportReport.columnstore-1.tar.gz     File columnstoreSupportReport.columnstore-2.tar.gz     File columnstoreSupportReport.columnstore-3.tar.gz     Text File strace.txt    

 Description   
  • Installed all packages from RPM repository for SLES 12.
  • Run postConfigure with single configuration
  • Try create test table: 

    CREATE TABLE
    		 
        `test`.table1
    		 
        (
    		 
            col1 INT
    		 
        )
    		 
        ENGINE=Columnstore DEFAULT CHARSET=latin1

  • Gets error: 

    [Code: 1815, SQL State: HY000]  (conn=11) Internal error: CAL0009: (5)Create table failed due to  IDB-2044: An internal error occurred.  Check the error log file & contact support.

We have installation of v1.2.2 on other systems openSUSE 42.3 but on real HW. And there is no problem with running.

 Comments   
Comment by Petr Procházka [ 2019-03-11 ]

I attached log files in columnstore.tar.gz.

Comment by Roman [ 2019-03-13 ]

Greetings Petr,

Something is wrong with dbroot 1 directory b/c there are lots of errors similar to this:
2019-03-11T15:46:04.073154+01:00 server-musp-bi IDBFile[16581]: 04.073088 |0|0|0| D 35 CAL0002: Failed to open file: /usr/local/mariadb/columnstore/data1/systemFiles/dbrm/BRM_saves_current, exception: unable to open Buffered file

Do you install CS as root or non-root? What is the file system behind /usr/local/mariadb/columnstore/data1/ ?

Comment by Petr Procházka [ 2019-03-13 ]

All RPM packages are installed as root user to / partition (default location /usr/local/mariadb/columnstore). All partitions are formatted with ext4 FS.
I only moved content of directory data1 to other directory and created symlink (data1 -> /mnt/olap/data1).
But if I thinking about it, RPMs are only installed then run postConfigure and I tried create table.

Comment by Roman [ 2019-03-13 ]

So are you able to create files and read from /usr/local/mariadb/columnstore/data1/ ?

Comment by Petr Procházka [ 2019-03-13 ]

Yes, I can read/write files, as root user.
There is permissions for installation root directory and data1 dir.

server-musp-bi:~/local/mariadb/columnstore # l
 
total 44
 
drwxr-xr-x 10 root  root  4096 Nov 29 05:42 ./
 
drwxr-xr-x  3 root  root  4096 Nov 29 05:42 ../
 
drwxr-xr-x  2 root  root  4096 Mar 13 15:52 bin/
 
drwxr-xr-x  3 root  root  4096 Mar 13 15:52 data/
 
drwxr-xr-x  4 root  root  4096 Mar 13 15:54 data1/
 
drwxr-xr-t  2 root  root  4096 Mar 13 15:55 etc/
 
drwxr-xr-x  2 root  root  4096 Mar 13 15:52 lib/
 
drwxr-xr-x  3 root  root  4096 Mar 13 15:52 local/
 
drwxr-xr-x 11 mysql mysql 4096 Mar 13 15:53 mysql/
 
drwxr-xr-x  2 root  root  4096 Mar 13 15:52 post/
 
-rw-r--r--  1 root  root    24 Nov 29 05:50 releasenum
 
server-musp-bi:~/local/mariadb/columnstore # l data1/
 
total 16
 
drwxr-xr-x  4 root root 4096 Mar 13 15:54 ./
 
drwxr-xr-x 10 root root 4096 Nov 29 05:42 ../
 
drwxr-xr-x  3 root root 4096 Mar 13 15:54 000.dir/
 
-rw-r--r--  1 root root    0 Mar 13 15:55 OAMdbrootCheck
 
drwxr-xr-t  3 root root 4096 Mar 13 15:52 systemFiles/
 
server-musp-bi:~/local/mariadb/columnstore # l data1/systemFiles/ -R
 
data1/systemFiles/:
 
total 12
 
drwxr-xr-t 3 root root 4096 Mar 13 15:52 ./
 
drwxr-xr-x 4 root root 4096 Mar 13 15:54 ../
 
drwxr-xr-x 2 root root 4096 Mar 13 15:54 dbrm/
 
 
 
data1/systemFiles/dbrm:
 
total 2108
 
drwxr-xr-x 2 root root    4096 Mar 13 15:54 ./
 
drwxr-xr-t 3 root root    4096 Mar 13 15:52 ../
 
-rw-rw-rw- 1 root root    3436 Mar 13 15:54 BRM_savesA_em
 
-rw-rw-rw- 1 root root      12 Mar 13 15:54 BRM_savesA_vbbm
 
-rw-rw-rw- 1 root root       8 Mar 13 15:54 BRM_savesA_vss
 
-rw-rw-rw- 1 root root    3372 Mar 13 15:54 BRM_savesB_em
 
-rw-rw-rw- 1 root root      12 Mar 13 15:54 BRM_savesB_vbbm
 
-rw-rw-rw- 1 root root       8 Mar 13 15:54 BRM_savesB_vss
 
-rw-rw-r-- 1 root root      10 Mar 13 15:54 BRM_saves_current
 
-rw-rw-rw- 1 root root    3436 Mar 13 15:54 BRM_saves_em
 
-rw-rw-rw- 1 root root       5 Mar 13 15:56 BRM_saves_journal
 
-rw-rw-rw- 1 root root      12 Mar 13 15:54 BRM_saves_vbbm
 
-rw-rw-rw- 1 root root       8 Mar 13 15:54 BRM_saves_vss
 
-rw-rw-r-- 1 root root      12 Mar 13 15:56 SMTxnID
 
-rw-rw-rw- 1 root root 2099202 Mar 13 15:53 oidbitmap
 
server-musp-bi:~/local/mariadb/columnstore #

Comment by Roman [ 2019-03-14 ]

There are two ways to deal with this: the short one and the long one.
The short is to try to reinstall CS from scratch wiping install dir.
The long way ia to discover what actually causes the error. I would appreciate if you choose the second and send me some debug info. If you will then run shell command just before you run that DDL statement:
strace -p ${pidof PrimProc} -e trace=file
Then finish strace and send me its output.

Comment by Petr Procházka [ 2019-03-18 ]

I already tried short way, no successful.

I called this statements and got this output.

server-musp-bi:~ # ps fax | grep PrimProc
 
 73156 pts/1    S+     0:00          \_ grep --color=auto PrimProc
 
 71536 ?        S<l    0:00      \_ [PrimProc]
 
server-musp-bi:~ # strace -p 71536 -e trace=file
 
Process 71536 attached
 
+++ killed by SIGSEGV (core dumped) +++

Comment by Roman [ 2019-03-19 ]

Ok, the output tells that we picked the correct daemon for investigation. You should add another key to the strace command to make it more clueful:
strace -p ${pidof PrimProc} -f -e trace=file
This -f flag allows us to look into all execution threads spawned by PrimProc. The procedure is the same: reinstall CS and run the strace right before CREATE TABLE statement.

Comment by Petr Procházka [ 2019-03-19 ]

I uninstalled all packages, deleted directory /usr/local/mariadb/columnstore and install all packages again and run postConfigure.
Output of strace is in file strace.txt.

Comment by Roman [ 2019-03-20 ]

The strace doesn't contain anything obvious as I expected so I better start once again from logs. Could I ask you for a support report tool output ?

Comment by Petr Procházka [ 2019-03-21 ]

Yes, it's np.

So I created clean installation and did these steps.

  • Uninstall all packages.
  • Delete directories /usr/local/mariadb and /var/log/mariadb.
  • Install all packages from repository.
  • Run postConfigure.
  • Connect to DB via mcsmysql and called CREATE TABLE SQL.
  • Run columnstoreSupport -a.

Today I got this output of MySQL console:

server-musp-bi:/usr/local/mariadb/columnstore # mcsmysql test
 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
 
Your MariaDB connection id is 10
 
Server version: 10.3.11-MariaDB-log Columnstore 1.2.2-1
 
 
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
 
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
 
 
MariaDB [test]> create table tab1(col1 int) engine=columnstore;
 
Query OK, 0 rows affected (2 min 0.404 sec)
 
 
 
MariaDB [test]>

Report output is in columnstoreSupportReport.columnstore-1.tar.gz.

Comment by Petr Procházka [ 2019-08-13 ]

So, I tried new release version 1.2.5.
Actually I tested on openSUSE 15.1 (as Hyper-V host) and got result of create table:

bi:~ # mcsmysql test
 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
 
Your MariaDB connection id is 11
 
Server version: 10.3.16-MariaDB-log Columnstore 1.2.5-1
 
 
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
 
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
 
 
MariaDB [test]> create table tab1(col1 int) engine=columnstore;
 
ERROR 1815 (HY000): Internal error: CAL0009: (5)Create table failed due to  IDB-2044: An internal error occurred.  Check the error log file & contact support.
 
MariaDB [test]> Bye

I attached new report output columnstoreSupportReport.columnstore-2.tar.gz

Comment by Petr Procházka [ 2019-08-13 ]

For our testing, I prepared new installation of openSUSE (latest 15.1) and tried install latest version 1.2.5.
Output of create table is OK:

boss-bi:~ # mcsmysql test
 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
 
Your MariaDB connection id is 10
 
Server version: 10.3.16-MariaDB-log Columnstore 1.2.5-1
 
 
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
 
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
 
 
MariaDB [test]> create table tab1(col1 int) engine=columnstore;
 
Query OK, 0 rows affected (0.410 sec)
 
 
 
MariaDB [test]> Bye

So I don't known what is wrong.

Report output is in columnstoreSupportReport.columnstore-3.tar.gz .

Comment by Petr Procházka [ 2023-07-18 ]

Pls close this issue. IMHO issue is not relevant now.

Generated at Thu Feb 08 02:34:41 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.