I’m on a mini pc with 16GB ram. On Bitcoin knots all good health but electrs keeps re starting when 49% sync I’m like a week like this.
Log:
2026-01-10T09:56:04+00:00 [2026-01-10T09:56:04.433Z INFO electrs::index] indexing 2000 blocks: [332001…334000]
2026-01-10T09:58:29+00:00 [2026-01-10T09:58:29.358Z INFO electrs::chain] chain updated: tip=000000000000000008d1ff7b7673837e9d7e1324dc7ab8498405ea583f43f53d, height=334000
2026-01-10T09:58:29+00:00 [2026-01-10T09:58:29.368Z INFO electrs::index] indexing 2000 blocks: [334001…336000]
2026-01-10T10:00:48+00:00 [2026-01-10T10:00:48.175Z INFO electrs::chain] chain updated: tip=0000000000000000125e3e6f327edcd7163b486efc16e79b8a996270127b54df, height=336000
2026-01-10T10:00:48+00:00 [2026-01-10T10:00:48.190Z ERROR electrs::server] 371: disconnecting due to failed to send response: “{"id":0,"jsonrpc":"2.0","result":["electrs/0.10.10","1.4"]}\n”
2026-01-10T10:00:48+00:00 [2026-01-10T10:00:48.190Z WARN electrs::server] 371: failed to shutdown TCP connection Transport endpoint is not connected (os error 107)
2026-01-10T10:00:48+00:00 [2026-01-10T10:00:48.200Z INFO electrs::index] indexing 2000 blocks: [336001…338000]
2026-01-10T10:02:49+00:00 [2026-01-10T10:02:49.418Z INFO electrs::chain] chain updated: tip=00000000000000001983dc4a87df627b63cdce28e5321cb867fbbb74c0e87e8e, height=338000
2026-01-10T10:02:49+00:00 [2026-01-10T10:02:49.428Z INFO electrs::index] indexing 2000 blocks: [338001…340000]
2026-01-10T10:05:12+00:00 [2026-01-10T10:05:12.814Z INFO electrs::signals] notified via SIG2
2026-01-10T10:05:15+00:00 [2026-01-10T10:05:15.565Z INFO electrs::db] closing DB at ./db/bitcoin
2026-01-10T10:13:34+00:00 Starting electrs 0.10.10 on x86_64 linux with Config { network: Bitcoin, db_path: “./db/bitcoin”, db_log_dir: None, db_parallelism: 1, daemon_auth: UserPass(“bitcoin”, “”), daemon_rpc_addr: 172.18.0.32:8332, daemon_p2p_addr: 172.18.0.32:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: “Welcome to electrs 0.10.10 (Electrum Rust Server)!”, signet_magic: f9beb4d9 }
2026-01-10T10:13:34+00:00 [2026-01-10T10:13:34.449Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
2026-01-10T10:13:34+00:00 [2026-01-10T10:13:34.449Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
2026-01-10T10:13:34+00:00 [2026-01-10T10:13:34.536Z INFO electrs::db] “./db/bitcoin”: 0 SST files, 0 GB, 0 Grows
2026-01-10T10:13:34+00:00 [2026-01-10T10:13:34.554Z INFO electrs::index] indexing 2000 blocks: [1…2000]
2026-01-10T10:13:34+00:00 [2026-01-10T10:13:34.866Z INFO electrs::chain] chain updated: tip=00000000dfd5d65c9d8561b4b8f60a63018fe3933ecb131fb37f905f87da951a, height=2000
2026-01-10T10:13:34+00:00 [2026-01-10T10:13:34.875Z INFO electrs::index] indexing 2000 blocks: [2001…4000]
2026-01-10T10:13:35+00:00 [2026-01-10T10:13:35.165Z INFO electrs::chain] chain updated: tip=00000000922e2aa9e84a474350a3555f49f06061fd49df50a9352f156692a842, height=4000
Hi @Lobocoin, thanks for sharing your Electrs logs. From what’s shown, it looks like StartOS is stopping Electrs rather than Electrs crashing on its own. To help move this forward, could you please share your StartOS logs from the same timeframe (especially just before the restart), and an updated set of Electrs logs covering that same period? That should help us identify why the service is being restarted.