Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.1.12
-
None
-
CentOS 6.9
Description
Folks,
It is something that I am noticing, and it's repeatable on CentOS 6.9. I'm using the below configurations for CLI:
[CLI]
|
type=service
|
router=cli
|
 |
[CLI Listener]
|
type=listener
|
service=CLI
|
protocol=maxscaled
|
port=6603 |
#socket=default |
I'm stopping maxscale and commenting the socket variable, adding port. When I stop it, the socket should go out, be removed by the process (right?). But, this is not happening by the way:
1. stop maxscale
2. comment socket, add port
3. start maxscale
You can see that socket is still there:
[root@box01 ~]# ls -lh /tmp/maxadmin* |
-rw-rw-rw- 1 root root 587 Dec 14 12:29 /tmp/maxadmin_output.txt |
srwxrwxrwx 1 maxscale maxscale 0 Dec 14 13:02 /tmp/maxadmin.sock |
Thanks, folks!