[MXS-1582] Maxscale leaving socket behind after shutdown Created: 2017-12-14  Updated: 2017-12-29  Resolved: 2017-12-29

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.1.12
Fix Version/s: 2.1.13, 2.2.1

Type: Bug Priority: Minor
Reporter: Wagner Bianchi (Inactive) Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None
Environment:

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!


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