[signet v22.0.0] Unable to sync node from scratch #32762

issue saravadeanil openend this issue on June 16, 2025
  1. saravadeanil commented at 1:02 pm on June 16, 2025: none

    Hi, I am trying to run bitcoin signet node with below configurations:-

    • Bitcore release:- v22.0.0

    • Parameters:-

     0            - '-chain=signet'
     1            - '-rest'
     2            - '-txindex'
     3            - '-disablewallet'
     4            - '-server'
     5            - '-rpcbind=0.0.0.0'
     6            - '-rpcport=38332'
     7            - '-rpcallowip=0.0.0.0/0'
     8            - '-rpcthreads=512'
     9            - '-rpcworkqueue=4096'
    10            - '-rpcuser=xxxxxxxxxx'
    11            - '-rpcpassword=xxxxxxxxxx'
    12            - '-dbcache=2048'
    13            - '-zmqpubrawtx=tcp://*:38333'
    14            - '-deprecatedrpc=addresses'
    15            - '-printtoconsole'
    

    My node is stuck with below logs:-

     02025-06-16T12:52:18Z init message: Loading P2P addresses
     12025-06-16T12:52:18Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
     22025-06-16T12:52:18Z loadblk thread exit
     32025-06-16T12:52:18Z Loaded 0 addresses from peers.dat  1ms
     42025-06-16T12:52:18Z Loaded 0 addresses from "anchors.dat"
     52025-06-16T12:52:18Z 0 block-relay-only anchors will be tried for connections.
     62025-06-16T12:52:18Z init message: Starting network threads
     72025-06-16T12:52:18Z net thread start
     82025-06-16T12:52:18Z dnsseed thread start
     92025-06-16T12:52:18Z addcon thread start
    102025-06-16T12:52:18Z init message: Done loading
    112025-06-16T12:52:18Z msghand thread start
    122025-06-16T12:52:18Z Loading addresses from DNS seed v7ajjeirttkbnt32wpy3c6w3emwnfr3fkla7hpxcfokr3ysd3kqtzmqd.onion:38333
    132025-06-16T12:52:18Z opencon thread start
    142025-06-16T12:52:18Z Loading addresses from DNS seed 178.128.221.177
    152025-06-16T12:52:18Z Loading addresses from DNS seed 2a01:7c8:d005:390::5
    162025-06-16T12:52:18Z 0 addresses found from DNS seeds
    172025-06-16T12:52:18Z dnsseed thread exit
    182025-06-16T12:52:19Z Cannot create socket for v7ajjeirttkbnt32wpy3c6w3emwnfr3fkla7hpxcfokr3ysd3kqtzmqd.onion:38333: unsupported network
    192025-06-16T12:53:19Z Adding fixed seeds as 60 seconds have passed and addrman is empty
    

    Any idea how to resolve it?

  2. mzumsande commented at 6:49 pm on June 16, 2025: contributor
    looks like you have no initial peers - if you don’t want to upgrade to a newer version, maybe addnode a current signet node to find an an initial peer that helps you bootstrap ( dig seed.signet.achownodes.xyz should return some).
  3. 0xB10C commented at 6:51 pm on June 16, 2025: contributor

    2025-06-16T12:52:18Z Loading addresses from DNS seed 178.128.221.177 2025-06-16T12:52:18Z Loading addresses from DNS seed 2a01:7c8:d005:390::5 2025-06-16T12:52:18Z 0 addresses found from DNS seeds

    the signet DNS seeds don’t seem to be returning addresses of peers for you to connect to and the hardcoded seeds in version v22 might be down too.

    Trying a more recent Bitcoin Core release might work, as it has more recent SigNet peers hardcoded.

  4. saravadeanil commented at 5:27 am on June 17, 2025: none
    Thanks for the suggestions, I tried to run the node with v26.0 and it started syncing 🎉
  5. saravadeanil closed this on Jun 17, 2025

  6. saravadeanil reopened this on Jun 30, 2025

  7. saravadeanil closed this on Jun 30, 2025


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-07-01 09:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me