Node startup failure

[blocknodehub]

/mnt/lndmain/core/bitcoind --version
Bitcoin Core version v25.0.0

https://github.com/lightningnetwork/lnd/releases/download/v0.17.3-beta/lnd-linux-amd64-v0.17.3-beta.tar.gz
/mnt/lndmain/core/lnd --version
lnd version 0.17.3-beta commit=v0.17.3-beta

bitcoin.conf
daemon=0
server=1
txindex=1
addressindex=1
timestampindex=1
spentindex=1
zmqpubrawtx=tcp://0.0.0.0:28333
zmqpubhashblock=tcp://0.0.0.0:28332
rpcallowip=0.0.0.0
rpcbind=0.0.0.0:8332
rpcport=8332
rpcuser=xxxx
rpcpassword=xxxx
rpcallowip=0.0.0.0/0.0.0.0
datadir=/mnt/lndmain/btcnode
maxmempool=1024
dbcache=2048
limitancestorcount=400
limitdescedantcount=400
limitdescendantcount=400
rpcworkqueue=1000

lnd.conf
[Application Options]

datadir=/.lnd/data
logdir=/.lnd/logs

[Bitcoin]

bitcoin.active=true
bitcoin.mainnet=true
bitcoin.node=bitcoind

[Bitcoind]

bitcoind.dir=/mnt/lndmain/btcnode
bitcoind.config=/mnt/lndmain/conf/bitcoin.conf
bitcoind.rpchost=0.0.0.0
bitcoind.rpcuser=xxxx
bitcoind.rpcpass=xxxx
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

Data on the btc node has been synchronized. An error occurs when starting the lnd node

/mnt/lndmain/core/lnd --configfile=/mnt/lndmain/conf/lnd.conf --debuglevel=debug

2023-12-08 18:09:55.900 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2023-12-08 18:09:55.900 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
2023-12-08 18:10:11.354 [DBG] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet] requested
2023-12-08 18:10:12.758 [INF] LNWL: Opened wallet
2023-12-08 18:10:12.828 [INF] CHRE: Primary chain is set to: bitcoin
2023-12-08 18:10:12.844 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on 127.0.0.1:28332
2023-12-08 18:10:12.844 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on 127.0.0.1:28333
2023-12-08 18:10:12.844 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
2023-12-08 18:10:12.850 [ERR] LTND: unable to create partial chain control: block notification over zmq is inactive on bitcoind
2023-12-08 18:10:12.850 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: block notification over zmq is inactive on bitcoind
2023-12-08 18:10:12.851 [INF] LTND: Shutdown complete

error creating wallet config: unable to create partial chain control: block notification over zmq is inactive on bitcoind

[microlancer]

Can you verify that zmq is active on bitcoind?

$ bitcoin-cli getzmqnotifications
[
  {
    "type": "pubrawblock",
    "address": "tcp://127.0.0.1:28332",
    "hwm": 1000
  },
  {
    "type": "pubrawtx",
    "address": "tcp://127.0.0.1:28333",
    "hwm": 1000
  }
]

[blocknodehub]

[blocknodehub]

The BTC zmq port is open

[bitromortac]

You use zmqpubhashblock=tcp://0.0.0.0:28332, what if you change it to zmqpubrawblock=tcp://0.0.0.0:28332 in your bitcoin.conf? (You expose a lot of endpoints with 0.0.0.0, double check if you really want to do so)

[microlancer]

Just a random thought here. I see in the configs this comment:

; ZMQ socket which sends rawblock and rawtx notifications from bitcoind. By
; default, lnd will attempt to automatically obtain this information, so this
; likely won't need to be set (other than for a remote bitcoind instance).

Do you get the same results if you remove the lines and let lnd detect it?

;bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
;bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

[blocknodehub]

If bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 is not set
Bitcoind. Zmqpubrawtx = TCP: / / 127.0.0.1:28333
Startup will get an error:
failed to load config: ValidateConfig: unable to load RPC credentials for bitcoind: please set bitcoind.rpcuser and bitcoind.rpcpass (or bitcoind.rpccookie) together with bitcoind.zmqpubrawblock, bitcoind.zmqpubrawtx

[blocknodehub]

I used --bitcoind.rpcpolling to start the sync
But how do I use btc nodes that are not on the same machine

[microlancer]

If your btc node is not on the same machine, you should specify the machine's IP in your lnd.conf

bitcoind.rpchost=1.2.3.4
bitcoind.zmqpubrawblock=tcp://1.2.3.4:28332
bitcoind.zmqpubrawtx=tcp://1.2.3.4:28333
bitcoind.rpcuser=xxx
bitcoind.rpcpass=xxx