Created
May 3, 2026 00:16
-
-
Save Victhereum/130990a86c61b61842e30cdbad035eda to your computer and use it in GitHub Desktop.
HAProxy logs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 2026-05-02T23:51:33.010204934Z [inf] [entrypoint] Substituting environment variables in HAProxy config... | |
| 2026-05-02T23:51:33.010210804Z [inf] [entrypoint] System DNS resolver: fd12::10 | |
| 2026-05-02T23:51:33.010218702Z [inf] [entrypoint] Waiting for emqx1.railway.internal to resolve (up to 60s)... | |
| 2026-05-02T23:51:33.010224128Z [inf] [entrypoint] DNS ready (or timeout reached). Starting HAProxy... | |
| 2026-05-02T23:51:33.010229793Z [inf] mqtt_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'railway_dns/dns1'. | |
| 2026-05-02T23:51:33.010233901Z [inf] mqtts_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010239314Z [inf] mqtt_ws_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010244209Z [err] [WARNING] (1) : mqtt_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'railway_dns/dns1'. | |
| 2026-05-02T23:51:33.010250199Z [err] [WARNING] (1) : mqtts_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010254327Z [err] [WARNING] (1) : mqtt_ws_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010258547Z [err] [WARNING] (1) : mqtt_ws_http_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010262839Z [err] [WARNING] (1) : emqx_dashboard_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010268113Z [err] [WARNING] (1) : mqtt_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'railway_dns/dns1'. | |
| 2026-05-02T23:51:33.010272718Z [inf] mqtt_ws_http_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.010278650Z [inf] emqx_dashboard_backend/emqx3: IP changed from '(none)' to 'fd12:dafa:1c10:0:1000:24:85c3:27a4' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011431746Z [inf] mqtt_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'railway_dns/dns1'. | |
| 2026-05-02T23:51:33.011436274Z [inf] mqtts_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011443054Z [inf] mqtt_ws_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011447286Z [err] [WARNING] (1) : mqtts_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011453499Z [err] [WARNING] (1) : mqtt_ws_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011457561Z [err] [WARNING] (1) : mqtt_ws_http_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011461691Z [inf] mqtt_ws_http_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011465866Z [inf] emqx_dashboard_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011470050Z [err] [WARNING] (1) : emqx_dashboard_backend/emqx1: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:12f:18d1:9312' by 'DNS cache'. | |
| 2026-05-02T23:51:33.011474402Z [inf] Server mqtt_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.011479131Z [err] [WARNING] (1) : Server mqtt_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.011483529Z [err] [WARNING] (1) : Server mqtt_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.011488149Z [inf] Server mqtt_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.011492742Z [inf] Server mqtts_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012416024Z [inf] Server mqtts_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012422461Z [inf] Server mqtt_ws_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012427255Z [inf] Server mqtt_ws_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012432044Z [err] [WARNING] (1) : Server mqtts_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012436178Z [err] [WARNING] (1) : Server mqtts_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012440202Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012444352Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012448576Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012452893Z [inf] Server mqtt_ws_http_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012456697Z [inf] Server mqtt_ws_http_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012461322Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012465180Z [inf] Server emqx_dashboard_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012468925Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx3 ('emqx3.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.012473353Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.012477334Z [inf] Server emqx_dashboard_backend/emqx3 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013676357Z [inf] Server mqtt_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013684877Z [inf] Server mqtt_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013690519Z [err] [WARNING] (1) : Server mqtt_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013696520Z [err] [WARNING] (1) : Server mqtt_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013701096Z [err] [WARNING] (1) : Server mqtts_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013705704Z [inf] Server mqtts_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013710559Z [inf] Server mqtts_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013714936Z [err] [WARNING] (1) : Server mqtts_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013720731Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013726433Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013731043Z [inf] Server mqtt_ws_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013735484Z [inf] Server mqtt_ws_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013739930Z [inf] Server mqtt_ws_http_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013744727Z [inf] Server mqtt_ws_http_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.013749124Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.013753834Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.015062070Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.015068744Z [inf] Server emqx_dashboard_backend/emqx1 ('emqx1.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.015074237Z [inf] Server emqx_dashboard_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.015079297Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx1 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.015085183Z [inf] mqtt_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'railway_dns/dns1'. | |
| 2026-05-02T23:51:33.015089979Z [inf] mqtts_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015094959Z [inf] mqtt_ws_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015099686Z [inf] mqtt_ws_http_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015105406Z [err] [WARNING] (1) : mqtt_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'railway_dns/dns1'. | |
| 2026-05-02T23:51:33.015110310Z [err] [WARNING] (1) : mqtts_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015115154Z [err] [WARNING] (1) : mqtt_ws_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015121030Z [err] [WARNING] (1) : mqtt_ws_http_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015125871Z [err] [WARNING] (1) : emqx_dashboard_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.015130794Z [inf] emqx_dashboard_backend/emqx2: IP changed from '(none)' to 'fd12:dafa:1c10:0:4000:134:1091:6dcb' by 'DNS cache'. | |
| 2026-05-02T23:51:33.016071397Z [inf] Server mqtt_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016080783Z [err] [WARNING] (1) : Server mqtt_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016085811Z [err] [WARNING] (1) : Server mqtt_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016090202Z [inf] Server mqtt_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016096141Z [err] [WARNING] (1) : Server mqtts_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016101506Z [inf] Server mqtts_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016105959Z [inf] Server mqtts_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016110222Z [err] [WARNING] (1) : Server mqtts_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016115587Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016120919Z [inf] Server mqtt_ws_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016125384Z [inf] Server mqtt_ws_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016129894Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016134309Z [inf] Server mqtt_ws_http_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016139110Z [inf] Server mqtt_ws_http_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.016143408Z [inf] Server emqx_dashboard_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.016148167Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.017394267Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.017400473Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx2 ('emqx2.railway.internal') is UP/READY (resolves again). | |
| 2026-05-02T23:51:33.017405009Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.017409480Z [inf] Server emqx_dashboard_backend/emqx2 administratively READY thanks to valid DNS answer. | |
| 2026-05-02T23:51:33.017413720Z [inf] Server mqtt_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused at initial connection step of tcp-check", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.017418825Z [err] [WARNING] (1) : Server mqtt_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused at initial connection step of tcp-check", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.017425502Z [inf] Server mqtt_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused at initial connection step of tcp-check", check duration: 5ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.017429428Z [err] [WARNING] (1) : Server mqtt_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused at initial connection step of tcp-check", check duration: 5ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.017433485Z [inf] Server mqtts_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 5ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.017437672Z [err] [WARNING] (1) : Server mqtts_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 5ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.137563306Z [inf] Server mqtts_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.137567619Z [err] [WARNING] (1) : Server mqtts_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.243205398Z [inf] Starting Container | |
| 2026-05-02T23:51:33.275240263Z [inf] Server mqtts_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.275245151Z [inf] backend mqtts_backend has no server available! | |
| 2026-05-02T23:51:33.275249088Z [err] [WARNING] (1) : Server mqtts_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.275255708Z [err] [ALERT] (1) : backend 'mqtts_backend' has no server available! | |
| 2026-05-02T23:51:33.405568801Z [inf] Server mqtt_ws_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.405573840Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.536396073Z [inf] Server mqtt_ws_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.536404745Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.673413183Z [inf] Server mqtt_ws_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.673420425Z [inf] backend mqtt_ws_backend has no server available! | |
| 2026-05-02T23:51:33.673425793Z [err] [WARNING] (1) : Server mqtt_ws_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.673430388Z [err] [ALERT] (1) : backend 'mqtt_ws_backend' has no server available! | |
| 2026-05-02T23:51:33.805797359Z [inf] Server mqtt_ws_http_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:33.805804867Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.004323256Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.004336198Z [inf] Server mqtt_ws_http_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.077088594Z [inf] Server mqtt_ws_http_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.077094137Z [inf] backend mqtt_ws_http_backend has no server available! | |
| 2026-05-02T23:51:34.077098505Z [err] [WARNING] (1) : Server mqtt_ws_http_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.077102552Z [err] [ALERT] (1) : backend 'mqtt_ws_http_backend' has no server available! | |
| 2026-05-02T23:51:34.203149921Z [inf] Server emqx_dashboard_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.203158621Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.337570583Z [inf] Server emqx_dashboard_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.337577407Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.474114326Z [err] [ALERT] (1) : backend 'emqx_dashboard_backend' has no server available! | |
| 2026-05-02T23:51:34.474125016Z [inf] Server emqx_dashboard_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.474130341Z [inf] backend emqx_dashboard_backend has no server available! | |
| 2026-05-02T23:51:34.474136437Z [err] [WARNING] (1) : Server emqx_dashboard_backend/emqx3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.608906231Z [inf] Server mqtt_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused at initial connection step of tcp-check", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.608910981Z [inf] backend mqtt_backend has no server available! | |
| 2026-05-02T23:51:34.608915593Z [err] [WARNING] (1) : Server mqtt_backend/emqx1 is DOWN, reason: Layer4 connection problem, info: "Connection refused at initial connection step of tcp-check", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. | |
| 2026-05-02T23:51:34.608923905Z [err] [ALERT] (1) : backend 'mqtt_backend' has no server available! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment