postConfigure failed with error:.UI Command log file cannot be opened

You are viewing an old version of this question. View the current version here.

i install column store and execute postConfigure, failed with the fallow msg:

Select the type of Data Storage [1=internal, 2=external, 4=hdfs] (1) > 1

Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) > 1


===== Performing Configuration Setup and MariaDB Columnstore Startup =====

NOTE: Setting 'NumBlocksPct' to 50%
      Setting 'TotalUmMemory' to 25% of total memory. Value set to 8G

Running the MariaDB Columnstore setup scripts

post-mysqld-install Successfully Completed
root is not in the sudoers file.  This incident will be reported.
post-mysql-install Successfully Completed

Starting MariaDB Columnstore Database Platform
root is not in the sudoers file.  This incident will be reported.

MariaDB Columnstore Database Platform Starting, please wait .UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened
.UI Command log file cannot be opened

looking forward somebody's help.

Answer Answered by David Thompson in this comment.

If you are still facing this issue, can you please file a bug in jira with more details? It would help to understand your environment, os, if this is docker etc. It does look like some kind of os permissions issue. also make sure the USER env var is set to root if you are logged in as root.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.