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

オープン
#2,074 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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時間
マージ済み PR(30日)
64

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートなし
  • コントリビューションガイドを読む

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

simplex-chat/simplexmq のほかの issue

simplex-chat/simplexmq の issue をすべて見る

似ている issue

Haskell の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。