[MCOL-1780] columnstore on docker fail create Created: 2018-10-07  Updated: 2018-10-10  Resolved: 2018-10-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.1.6
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: thomas lloancy Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

archlinux


 Description   

On debian system this very
docker run -d --name mcs mariadb/columnstore
docker exec -it mcs bash

seems to work well with no problem about columnstore engine tables creation.

But on arch here what happens when try to create the same:

MariaDB [new]> create table zerty(region_id int, nom varchar(255))engine=columnstore;
ERROR 1815 (HY000): Internal error: CAL0009: (2)Create table failed due to WE: Error updating calpontsys.systable: opening a column file. The file was not found or was inaccessible.

The dbbuild 7 trick doesn't work.

Thanks

tll

 Comments   
Comment by thomas lloancy [ 2018-10-07 ]

And now:

*ERROR 1815 (HY000): Internal error: CAL0009: (2)Create table failed due to WE: Error updating calpontsys.systable: opening a column file. The file was not found or was inaccessible.
MariaDB [test]> use calpontsys
Database changed
MariaDB [calpontsys]> show tables;
----------------------

Tables_in_calpontsys

----------------------

syscolumn
systable

----------------------
2 rows in set (0.04 sec)

MariaDB [calpontsys]> select * from systable limit 2;
Empty set (50.46 sec)

MariaDB [calpontsys]> select * from syscolumn limit 2;
Empty set (0.05 sec)

MariaDB [calpontsys]> select * from systable limit 2;
Empty set (50.40 sec)

MariaDB [calpontsys]> create table toto(uh int, ok varchar(5))engine=columnstore;
ERROR 1815 (HY000): Internal error: Calpont system tables can only be created with 'SCHEMA SYNC ONLY'*

Comment by thomas lloancy [ 2018-10-07 ]

maybe found the answer mysqlf...

[solid@metalgear ~]$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
dev 3,9G 0 3,9G 0% /dev
run 3,9G 1000K 3,9G 1% /run
/dev/sda2 99G 93G 588M 100% /
tmpfs 3,9G 94M 3,8G 3% /dev/shm
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
tmpfs 3,9G 162M 3,7G 5% /tmp
/dev/sda4 810G 657G 113G 86% /home
/dev/sda1 511M 44M 468M 9% /boot
tmpfs 787M 12K 787M 1% /run/user/1000

Comment by David Thompson (Inactive) [ 2018-10-07 ]

could be - also check docker logs mcs as the postConfigure script is run as part of the entrypoint script. Most likely it should show an error like out of disk. Depending on how much dockering you have been doing try docker volume prune as well as cleaning up images.

Comment by David Thompson (Inactive) [ 2018-10-07 ]

was this the issue?

Comment by thomas lloancy [ 2018-10-09 ]

yep 100%

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