service name does not exist (Temporary failure in name resolution)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 32/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- haskell
- 領域
- networking
研究方向
Start at src/Simplex/Messaging/Server.hs:1555, where the connect error is logged, and trace how a client address is resolved and how a failed connection is retried or abandoned. The reported symptom is that resolution failures leave the server unable to reconnect until restart, so compare that retry path with the Docker DNS behaviour described for the self-hosted deployment. Done looks like the server recovering on its own after a transient getAddrInfo failure, verified by reproducing the failure in a test or local Docker setup rather than a one-line change.
由索引模型根據 Issue 內容生成。
描述
I am experiencing intermittent issues with my self-hosted SMP server where messages are neither sent nor received reliably.
The issue has occurred with both the current release (v7.1.0.18) and the previous release.
When checking the server logs, I see the followijng warning:
[WARN 2026-11-15 12:58:22 +0000 src/Simplex/Messaging/Server.hs:1555] Error connecting: smp18.simplex.im,lyqpnwbs2zqfr45jqkncwpywpbtq7jrhxnib5qddtr6npjyezuwd3nqd.onion PCENetworkError (NEConnectError {connectError = "Network.Socket.getAddrInfo (called with preferred socket type/protocol: AddrInfo {addrFlags = [], addrFamily = AF_UNSPEC, addrSocketType = Stream, addrProtocol = 0, addrAddress = 0.0.0.0:0, addrCanonName = Nothing}, host name: Just \"smp18.simplex.im\", service name: Just \"5223\"): does not exist (Temporary failure in name resolution)"})
The error appears to indicate a temporary DNS resolution failure when the server attempts to resolve smp18.simplex.im. The same also happens when trying to resolve my own internal smp-server via FQDN.
Environment:
- Deployment: Self-hosted SMP server running in Docker
- SMP server version: 7.1.0.18
- Previous version: Same issue observed with the previous release
Observed behavior
- The server stops sending and recieving messages, but client reports no connection problems to it.
- The logs contain repeated DNS resolution errors when attempting to connect to the smp-servers FQDN and other SMP servers.
- Restarting the smp-server docker container resolves the issue.
The issue has been observed across two consecutive releases.
Expected behaviour
The SMP server should maintain reliable connectivity to other SMP servers and recover gracefully from temporary DNS resolution failures without requiring a manual container restart.
Happy to provide additional logs or configuration details if needed.
- 主要語言
- Haskell
- 星號
- 865
- 分支
- 125
- 平均合併
- 1 天 20 小時
- 30 天內合併 PR
- 64
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
simplex-chat/simplexmq 的其他 Issue
-
xftp CLI: Generated web link is missing the /file path可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
simplex-chat/simplexmq#1853 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
simplex-chat/simplexmq#1781 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 35/100
simplex-chat/simplexmq#2017 ·
維護者通常 1 天內回覆
-
resolver: resolve .simplex names, on smp7 and then on the preset routers可能已有人在做 @shumvgolove 於 18 天前認領。 未關閉
simplex-chat/simplexmq#2011 · 2 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 30/100
simplex-chat/simplexmq#1864 ·
維護者通常 1 天內回覆
查看 simplex-chat/simplexmq 的全部 Issue
相似的 Issue
-
bug desktop
難度 2/5 1-3 小時 新手友好度 85/100
simplex-chat/simplex-chat#8291 ·
維護者通常 1 天內回覆
-
[BUG]: C# programs with top-level statements fail to compile可能已有人在做 @AsyncNigam 今天認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 76/100
compiler-explorer/compiler-explorer#9625 · 1 則留言 ·
維護者通常 1 天內回覆
-
needs triage type: enhancement
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 3 天內回覆
-
reflex-0.10未關閉
難度 1/5 1 小時以內 新手友好度 62/100
commercialhaskell/stackage#8180 ·
維護者通常 1 天內回覆
-
documentation
難度 2/5 1-3 小時 新手友好度 78/100
OpenZeppelin/canton-contracts#140 ·
維護者通常 1 天內回覆