Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
This error is being returned if IPC is specified instead of tpc:
Error: Invalid port specified in -zmqpubrawtx: ‘ipc:///root/snap/bitcoin-core/common/.bitcoin/bitcoind.tx.raw
Expected behaviour
IPC should correctly work
Steps to reproduce
0# cat ~/snap/bitcoin-core/common/.bitcoin/bitcoin.conf
1
2server=1
3rpcuser=<censored>
4rpcpassword=<censored>
5zmqpubhashtx=tcp://127.0.0.1:29000
6zmqpubhashblock=tcp://127.0.0.1:29001
7zmqpubrawblock=tcp://127.0.0.1:29002
8zmqpubsequence=tcp://127.0.0.1:29004
9zmqpubrawtx=ipc:///root/snap/bitcoin-core/common/.bitcoin/bitcoind.tx.raw
Relevant log output
02024-04-04T07:58:25Z Bitcoin Core version v26.0.0 (release build)
12024-04-04T07:58:25Z Using the 'x86_shani(1way,2way)' SHA256 implementation
22024-04-04T07:58:25Z Using RdSeed as an additional entropy source
32024-04-04T07:58:25Z Using RdRand as an additional entropy source
42024-04-04T07:58:25Z Default data directory /root/snap/bitcoin-core/common/.bitcoin
52024-04-04T07:58:25Z Using data directory /root/snap/bitcoin-core/common/.bitcoin
62024-04-04T07:58:25Z Config file: /root/snap/bitcoin-core/common/.bitcoin/bitcoin.conf
72024-04-04T07:58:25Z Config file arg: rpcpassword=****
82024-04-04T07:58:25Z Config file arg: rpcuser=****
92024-04-04T07:58:25Z Config file arg: server="1"
102024-04-04T07:58:25Z Config file arg: zmqpubhashblock="tcp://127.0.0.1:29001"
112024-04-04T07:58:25Z Config file arg: zmqpubhashtx="tcp://127.0.0.1:29000"
122024-04-04T07:58:25Z Config file arg: zmqpubrawblock="tcp://127.0.0.1:29002"
132024-04-04T07:58:25Z Config file arg: zmqpubrawtx="ipc:///root/snap/bitcoin-core/common/.bitcoin/bitcoind.tx.raw"
142024-04-04T07:58:25Z Config file arg: zmqpubsequence="tcp://127.0.0.1:29004"
152024-04-04T07:58:25Z Using at most 125 automatic connections (65536 file descriptors available)
162024-04-04T07:58:25Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
172024-04-04T07:58:25Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
182024-04-04T07:58:25Z Script verification uses 15 additional threads
192024-04-04T07:58:25Z scheduler thread start
202024-04-04T07:58:25Z Binding RPC on address ::1 port 8332
212024-04-04T07:58:25Z Binding RPC on address 127.0.0.1 port 8332
222024-04-04T07:58:25Z [http] creating work queue of depth 16
232024-04-04T07:58:25Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
242024-04-04T07:58:25Z [http] starting 4 worker threads
252024-04-04T07:58:25Z Using wallet directory /root/snap/bitcoin-core/common/.bitcoin/wallets
262024-04-04T07:58:25Z init message: Verifying wallet(s)…
272024-04-04T07:58:25Z Using /16 prefix for IP bucketing
282024-04-04T07:58:25Z init message: Loading P2P addresses…
292024-04-04T07:58:25Z Loaded 63406 addresses from peers.dat 101ms
302024-04-04T07:58:25Z init message: Loading banlist…
312024-04-04T07:58:25Z SetNetworkActive: true
322024-04-04T07:58:25Z Error: Invalid port specified in -zmqpubrawtx: 'ipc:///root/snap/bitcoin-core/common/.bitcoin/bitcoind.tx.raw'
33Error: Invalid port specified in -zmqpubrawtx: 'ipc:///root/snap/bitcoin-core/common/.bitcoin/bitcoind.tx.raw'
342024-04-04T07:58:25Z Shutdown: In progress...
352024-04-04T07:58:25Z scheduler thread exit
362024-04-04T07:58:25Z Flushed fee estimates to fee_estimates.dat.
372024-04-04T07:58:25Z Shutdown: done
How did you obtain Bitcoin Core
Other
What version of Bitcoin Core are you using?
v26.0.0
Operating system and version
Ubuntu 22.04.4 LTS
Machine specifications
No response
