guogm: reason: {shutdown,tcp_closed} 这种tcp_closed 一般比较难查。EMQX 这边是发现 Socket 异常关闭了,才会打印这个日志,并关闭这个客户端连接。可能是由于: 客户端进程异常关闭了 Socket 中间的网络设备或者程序,异常关闭了 Socket 建议是通过 tcpdump 或者 Wireshark 抓包,检查下 TCP 的 FIN 是谁先发起的。
根据日志追踪发现有些设备不断的连接又立马断开 reason: {shutdown,tcp_closed}, 正常下线日志是 emqx_connection_terminated, reason: {shutdown,normal} 2023-03-18T18:25:02+08:00 [MQTT] P566511OPBP@183.171.78.210:47926 msg: mqtt_packet_received, packet: CONNECT(Q0, R0, D0, ClientId=P566511O...
[error] supervisor: 'esockd_connection_sup - <0.3265.0>', errorContext: connection_shutdown, reason: {recv_proxy_info_error,tcp_closed}, offender: 修复后不再打印任何日志,但仍然可以通过 emqx_ctl listeners 命令来查看错误原因的统计。 改进监听器针对文件描述符耗尽的错误日志 emqx/esockd#173。 改进...
所以,当发现 EMQX 日志中出现tcp_closed,并且这一断开连接的行为并不是你期望的时,建议排查客户端的实现是否存在问题。 #关键字:“maximum heap size reached“ 出现这一日志说明当前客户端进程占用的堆栈已经超过了预设的最大值,客户端进程将被强制杀死以保证 EMQX 的可用性,避免客户端进程的内存占用无限制增长最终...
{ "username": "foo", "ts": 1625572213873, "sockport": 1883, "reason": "tcp_closed", "proto_ver": 4, "proto_name": "MQTT", "ipaddress": "127.0.0.1", "disconnected_at": 1625572213873, "clientid": "emqtt-8348fe27a87976ad4db3" } EMQX 默认只允许本机的 MQTT 客户端订阅 $SYS 主...
connection is "Terminated due to {shutdown,tcp_closed}",but next Non-normal connection ,Not certified,can reponse hearbeat to client ,so client don't think it disconnected.result in this equipment cycle is stuck in constant reconnectio
"reason":"tcp_closed", "disconnected_at":1582688032, "clientid":"emqtt-8348fe27a87976ad4db3" } 1. 2. 3. 4. 5. 6. 7. 当然在开发的时候我们订阅两个主题比较麻烦,在这里我们可以采用主题通配符模式直接订阅一个主题即可: $SYS/brokers/+/clients/# ...
payload :map[clientid:xxx_642874 disconnected_at:1.603525402882e+12 reason:tcp_closed ts:1.603525402882e+12 username:undefined] xxxx_642874这个为下线的clientID 可以通过这个来处理离线逻辑 emqx官方文档 修改etc/acl.conf 如果担心其他人非法获取离线消息,可以设置订阅权限 ...
Environment OS: docker Erlang/OTP: EMQ: 2.1.2 Description There are a lot of errors in the error.log 2017-07-28 09:38:34.352 [error] <0.1181.0> Connection Id 1482704 closing with reason: tcp_closed 2017-07-28 09:38:34.352 [error] <0.1181...
(memsup): Erlang has closed^M43[os_mon] cpu supervisor port (cpu_sup): Erlang has closed^M44{"Kernel pid terminated",application_controller,"{application_start_failure,emqx,{bad_return,{{emqx_app,start,[normal,[]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,emqx_...