The process that fails to listen does not exit?

[Fiekers]

Listen "external/0.0.0.0:1883" failed on 0.0.0.0:1883, IoError(Os { code: 98, kind: AddrInUse, message: "Address already in use" })

[rmqtt]

Can you provide a detailed description of the scenario that caused this problem, so that I can reproduce it.

…

---- Replied Message ---- | From | ***@***.***> | | Date | 04/28/2024 11:41 | | To | ***@***.***> | | Cc | ***@***.***> | | Subject | [rmqtt/rmqtt] listen failed process not exist? (Issue #58) | Listen "external/0.0.0.0:1883" failed on 0.0.0.0:1883, IoError(Os { code: 98, kind: AddrInUse, message: "Address already in use" }) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Fiekers]

[rmqtt]

In the ntex framework, reuseaddr is set to true by default, but reuseport is not set to true, so see if there are any processes occupying port 1883. That is to say, it has not completely exited after starting rmqtt last time. You can wait for a while and try again to see if this error will still be reported.

…

---- Replied Message ---- | From | ***@***.***> | | Date | 04/29/2024 11:23 | | To | ***@***.***> | | Cc | ***@***.***>***@***.***> | | Subject | Re: [rmqtt/rmqtt] The process that fails to listen does not exit? (Issue #58) | _1714360987652.png (view on web) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[Fiekers]

How to exit the program when the port is occupied

[rmqtt]

Currently we can only kill the process directly, and we will consider the implementation of graceful exit later.

…

---- Replied Message ---- | From | ***@***.***> | | Date | 04/29/2024 11:45 | | To | ***@***.***> | | Cc | ***@***.***>***@***.***> | | Subject | Re: [rmqtt/rmqtt] The process that fails to listen does not exit? (Issue #58) | How to exit the program when the port is occupied — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[timzaak]

This would always happen when exec docker restart mqtt after client has connected.
may add signal::ctrl_c() broadcast queue, and close all resources after receive the message.
just like rathole project does.

[rmqtt]

Thank you for reporting this issue. However, I was unable to reproduce the problem. I performed the following commands: docker restart rmqtt or docker-compose restart In both cases, the client was able to reconnect successfully. I tested this on a single-node setup. Could you please provide more details about the issue? Specifically, whether you are using a single node or a cluster, the version of rmqtt, whether you are using docker-compose or directly starting the container with docker, and what client tool you are using.

…

---- Replied Message ---- | From | ***@***.***> | | Date | 05/22/2024 10:22 | | To | ***@***.***> | | Cc | ***@***.***>***@***.***> | | Subject | Re: [rmqtt/rmqtt] The process that fails to listen does not exit? (Issue #58) | This would always happen when exec docker restart mqtt and client is connecting. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[timzaak]

All config and run bash here: https://github.com/ForNetCode/mqtt-exec/tree/master/shell/prod

$ uname -a
Linux 10-23-70-251 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ docker restart rmqtt 
rmqtt
$ docker logs --tail 10 rmqtt
024-05-22 03:40:30.968 ERRO rmqttd.189 | Listen "external/0.0.0.0:1883" failed on 0.0.0.0:1883, IoError(Os { code: 98, kind: AddrInUse, message: "Address in use" })
2024-05-22 03:40:30.968 INFO rmqtt_http_api::api.98 | HTTP API Listening on 0.0.0.0:6060, reuseaddr: true, reuseport: false
2024-05-22 03:40:30.969 INFO rmqtt::grpc::server.29 | gRPC server is listening on tcp://0.0.0.0:5363, reuseaddr: true, reuseport: false

After about 5 mins, docker restart would be ok.

[rmqtt]

rmqtt.toml中添加"reuseport"配置试试： ## MQTT/TCP - External TCP Listener for MQTT Protocol listener.tcp.external.addr = "0.0.0.0:1883" listener.tcp.external.reuseport = true

…

---- Replied Message ---- | From | ***@***.***> | | Date | 05/22/2024 11:43 | | To | ***@***.***> | | Cc | ***@***.***>***@***.***> | | Subject | Re: [rmqtt/rmqtt] The process that fails to listen does not exit? (Issue #58) | All config and run bash here: https://github.com/ForNetCode/mqtt-exec/tree/master/shell/prod $ uname -a Linux 10-23-70-251 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ docker restart rmqtt rmqtt $ docker logs --tail 10 rmqtt 024-05-22 03:40:30.968 ERRO rmqttd.189 | Listen "external/0.0.0.0:1883" failed on 0.0.0.0:1883, IoError(Os { code: 98, kind: AddrInUse, message: "Address in use" }) 2024-05-22 03:40:30.968 INFO rmqtt_http_api::api.98 | HTTP API Listening on 0.0.0.0:6060, reuseaddr: true, reuseport: false 2024-05-22 03:40:30.969 INFO rmqtt::grpc::server.29 | gRPC server is listening on tcp://0.0.0.0:5363, reuseaddr: true, reuseport: false — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[timzaak]

2024-05-22 06:01:21.803 INFO rmqtt_http_api::api.98 | HTTP API Listening on 0.0.0.0:6060, reuseaddr: true, reuseport: false
2024-05-22 06:01:21.804 INFO rmqtt::grpc::server.29 | gRPC server is listening on tcp://0.0.0.0:5363, reuseaddr: true, reuseport: false
2024-05-22 06:02:19.618 INFO rmqtt::settings.114 | node_id is 1
2024-05-22 06:02:19.618 INFO rmqtt::settings.115 | exec_workers is 200
2024-05-22 06:02:19.618 INFO rmqtt::settings.116 | exec_queue_max is 3000
2024-05-22 06:02:19.618 INFO rmqtt::settings.117 | local_exec_workers is 5
2024-05-22 06:02:19.618 INFO rmqtt::settings.118 | local_exec_queue_max is 1000
2024-05-22 06:02:19.618 INFO rmqtt::settings.119 | local_exec_rate_limit is (100, 1s)
2024-05-22 06:02:19.619 INFO rmqtt::settings.120 | node.busy config is: Busy { check_enable: true, update_interval: 2s, loadavg: 80.0, cpuloadavg: 90.0, handshaking: 0 }
2024-05-22 06:02:19.620 INFO rmqtt_acl.50 | rmqtt-acl init
2024-05-22 06:02:19.620 INFO rmqtt_acl.79 | rmqtt-acl start
2024-05-22 06:02:19.620 INFO rmqtt_counter.34 | rmqtt-counter init
2024-05-22 06:02:19.620 INFO rmqtt::grpc::server.29 | gRPC server is listening on tcp://0.0.0.0:5363, reuseaddr: true, reuseport: false
2024-05-22 06:02:19.620 INFO rmqtt_counter.97 | rmqtt-counter start
2024-05-22 06:02:19.620 INFO rmqtt_http_api.85 | rmqtt-http-api init
2024-05-22 06:02:19.620 INFO rmqtt_http_api.122 | rmqtt-http-api start
2024-05-22 06:02:19.620 INFO rmqtt_http_api::api.98 | HTTP API Listening on 0.0.0.0:6060, reuseaddr: true, reuseport: false
2024-05-22 06:02:19.620 ERRO rmqttd.189 | Listen "external/0.0.0.0:1883" failed on 0.0.0.0:1883, IoError(Os { code: 98, kind: AddrInUse, message: "Address in use" })

same error with listener.tcp.external.reuseport = true