Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
-
1.0.6
-
None
Description
When you use the docker image, you'll see these logs:
mv: cannot stat '/var/log/mariadb/columnstore/ProcessManager.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/ProcessManager.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DBRMControllerNode.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DBRMControllerNode.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/ServerMonitor.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/ServerMonitor.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DBRMWorkerNode.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DBRMWorkerNode.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DecomSvr.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DecomSvr.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/PrimProc.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/PrimProc.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/ExeMgr.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/ExeMgr.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/WriteEngineServer.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/WriteEngineServer.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DDLProc.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DDLProc.err': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DMLProc.out': No such file or directory
|
mv: cannot stat '/var/log/mariadb/columnstore/DMLProc.err': No such file or directory
|
This corresponds to some logic around 2444 in processmonitor.cpp where it tries to do these actual mvs as system calls. Also there is an if condition where it seems to do the same in both conditions. I suspect this code can just be removed or if this is a possibility should update this to check the file actually exists (and maybe not use a system call..).