service name does not exist (Temporary failure in name resolution)

未关闭
#2,074 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 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 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

simplex-chat/simplexmq 的其他 Issue

查看 simplex-chat/simplexmq 的全部 Issue

相似的 Issue

更多 Haskell Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。