Closed berkutx closed 3 years ago
Can anyone confirm that zmq works in the release version of the wallet. Specifically: ./pivxd -zmqpubrawtx=tcp://IP:PORT
I check it on: https://github.com/PIVX-Project/PIVX/releases/download/v5.0.1/pivx-5.0.1-x86_64-linux-gnu.tar.gz and compile from sources by ./configure --with-zmq --without-gui --with-miniupnpc=no
./configure --with-zmq --without-gui --with-miniupnpc=no
rpcuser=********************4 rpcpassword=4************** rpcport=PORT rpcallowip=IP zmqpubrawtx=tcp://*IP:PORT* server=1 daemon=1 logtimestamps=1 maxconnections=256
2021-02-03 20:46:10 PIVX version v5.0.1.0-g641b107ea24ff1077e6f5047bffc2f54f91e2a14 (release build) (Thu, 14 Jan 2021 09:15:35 -0800) 2021-02-03 20:46:10 Using RdRand as an additional entropy source 2021-02-03 20:46:10 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2021-02-03 20:46:10 Default data directory /root/.pivx 2021-02-03 20:46:10 Using data directory /root/.pivx 2021-02-03 20:46:10 Using config file /root/.pivx/pivx.conf 2021-02-03 20:46:10 Using at most 256 connections (1024 file descriptors available) 2021-02-03 20:46:10 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2021-02-03 20:46:10 Using 0 threads for script verification 2021-02-03 20:46:10 scheduler thread start 2021-02-03 20:46:11 Loaded Sapling parameters in 0.294675s seconds. 2021-02-03 20:46:11 Binding RPC on address 0.0.0.0 port 51473 failed. 2021-02-03 20:46:11 HTTP: creating work queue of depth 16 2021-02-03 20:46:11 HTTP: starting 4 worker threads 2021-02-03 20:46:11 Creating backup of "/root/.pivx/wallet.dat" -> "/root/.pivx/backups/wallet.dat.2021-02-03-20-46" 2021-02-03 20:46:11 init message: Verifying wallet... 2021-02-03 20:46:11 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2021-02-03 20:46:11 Using wallet wallet.dat 2021-02-03 20:46:11 CDBEnv::Open: LogDir=/root/.pivx/database ErrorFile=/root/.pivx/db.log 2021-02-03 20:46:11 Bound to [::]:51472 2021-02-03 20:46:11 Bound to 0.0.0.0:51472 2021-02-03 20:46:11 Cache configuration: 2021-02-03 20:46:11 * Using 12.5MiB for block index database 2021-02-03 20:46:11 * Using 29.9MiB for chain state database 2021-02-03 20:46:11 * Using 57.6MiB for in-memory UTXO set 2021-02-03 20:46:11 Opening LevelDB in /root/.pivx/zerocoin 2021-02-03 20:46:11 Opened LevelDB successfully 2021-02-03 20:46:11 Opening LevelDB in /root/.pivx/sporks 2021-02-03 20:46:11 Opened LevelDB successfully 2021-02-03 20:46:11 Opening LevelDB in /root/.pivx/blocks/index 2021-02-03 20:46:11 Opened LevelDB successfully 2021-02-03 20:46:11 Opening LevelDB in /root/.pivx/chainstate 2021-02-03 20:46:11 Opened LevelDB successfully 2021-02-03 20:46:11 init message: Upgrading coins database... 2021-02-03 20:46:11 Upgrading database... 2021-02-03 20:46:11 init message: Loading sporks... 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_5_MAX_VALUE with value 1000 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT with value 1591401600 : Sat Jun 6 00:00:00 2020 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_9_MASTERNODE_BUDGET_ENFORCEMENT with value 1 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_13_ENABLE_SUPERBLOCKS with value 1 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_14_NEW_PROTOCOL_ENFORCEMENT with value 1591390800 : Fri Jun 5 21:00:00 2020 2021-02-03 20:46:11 LoadSporksFromDB : Spork 15 signed at 1611797460 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_15_NEW_PROTOCOL_ENFORCEMENT_2 with value 1611887400 : Fri Jan 29 02:30:00 2021 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_16_ZEROCOIN_MAINTENANCE_MODE with value 1606842000 : Tue Dec 1 17:00:00 2020 2021-02-03 20:46:11 LoadSporksFromDB : loaded spork SPORK_18_ZEROCOIN_PUBLICSPEND_V4 with value 1578346098 : Mon Jan 6 21:28:18 2020 2021-02-03 20:46:11 init message: Loading block index... 2021-02-03 20:46:33 LoadBlockIndexDB: last block file = 127 2021-02-03 20:46:33 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=68244, size=52787769, heights=2638601...2706842, time=2020-12-17...2021-02-03) 2021-02-03 20:46:33 Checking all blk files are present... 2021-02-03 20:46:34 LoadBlockIndexDB: Last shutdown was prepared: true 2021-02-03 20:46:34 LoadBlockIndexDB(): transaction index enabled 2021-02-03 20:46:35 LoadBlockIndexDB(): hashBestChain=fadb01a287877c2a5e660de391cfca46cbb98ec6d34b230d3daf5e34db3492d8 height=2706842 date=2021-02-03 20:42:00 progress=0.999995 2021-02-03 20:46:35 init message: Verifying blocks... 2021-02-03 20:46:35 Verifying last 10 blocks at level 4 2021-02-03 20:46:35 CheckBlock: Masternode/Budget payment checks skipped on sync 2021-02-03 20:46:35 No coin database inconsistencies in last 11 blocks (25 transactions) 2021-02-03 20:46:35 block index 24072ms 2021-02-03 20:46:35 init message: Loading wallet..... .....
Can confirm it on master. Just added the zmq functional test to the testing suite in #2190 and it's passing.
Closing this, don't hesitate on writing your feedback.
Can anyone confirm that zmq works in the release version of the wallet. Specifically: ./pivxd -zmqpubrawtx=tcp://IP:PORT
What version of PIVX Core are you using?
I check it on: https://github.com/PIVX-Project/PIVX/releases/download/v5.0.1/pivx-5.0.1-x86_64-linux-gnu.tar.gz and compile from sources by
./configure --with-zmq --without-gui --with-miniupnpc=no
Machine specs:
Log & config: