[MXS-3699] MaxCtrl reads .maxctrl.cnf from incorrect path Created: 2021-07-29  Updated: 2021-07-29  Resolved: 2021-07-29

Status: Closed
Project: MariaDB MaxScale
Component/s: maxctrl
Affects Version/s: 6.1.0
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Geoff Montee (Inactive) Assignee: markus makela
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MXS-3697 MaxCtrl config file check fails when ... Closed

 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)



 Comments   
Comment by markus makela [ 2021-07-29 ]

This is a duplicate of MXS-3697.

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