Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
6.1.0
-
None
Description
Depending on your current working directory, MaxCtrl may sometimes try to read .maxctrl.cnf from an incorrect path.
To reproduce:
$ cd /
|
$ strace -o ~/strace.out -ff maxctrl list service
|
You will see the following error message:
ENOENT: no such file or directory, stat '/~/.maxctrl.cnf'
|
And the strace output will show:
$ grep "\.maxctrl.cnf" ~/strace.out.*
|
/home/ec2-user/strace.out.1731:stat("/~/.maxctrl.cnf", 0x7fff4727d5b0) = -1 ENOENT (No such file or directory)
|
/home/ec2-user/strace.out.1731:stat("/~/.maxctrl.cnf", 0x7fff4727d200) = -1 ENOENT (No such file or directory)
|
/home/ec2-user/strace.out.1731:stat("/~/.maxctrl.cnf", 0x7fff4727ce40) = -1 ENOENT (No such file or directory)
|
Attachments
Issue Links
- duplicates
-
MXS-3697 MaxCtrl config file check fails when executed from the root directory
- Closed