zmq: log outbound message high water mark when reusing socket #15209

pull fanquake wants to merge 1 commits into bitcoin:master from fanquake:zmq-always-log-high-water-mark changing 1 files +1 −0
  1. fanquake commented at 2:13 PM on January 19, 2019: member

    Running master with src/bitcoind -zmqpubhashblockhwm=12345 -zmqpubrawtx=tcp://127.0.0.1:28332 -zmqpubhashtxhwm=5000 -zmqpubrawblock=tcp://127.0.0.1:28332 -zmqpubhashtx=tcp://127.0.0.1:28332 -zmqpubhashblock=tcp://127.0.0.1:28332 -debug=zmq:

    2019-01-19T14:11:01Z zmq: version 4.3.1
2019-01-19T14:11:01Z zmq: Initialize notification interface
2019-01-19T14:11:01Z zmq: Outbound message high water mark for pubhashblock at tcp://127.0.0.1:28332 is 12345
2019-01-19T14:11:01Z zmq: Notifier pubhashblock ready (address = tcp://127.0.0.1:28332)
2019-01-19T14:11:01Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-19T14:11:01Z zmq: Notifier pubhashtx ready (address = tcp://127.0.0.1:28332)
2019-01-19T14:11:01Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-19T14:11:01Z zmq: Notifier pubrawblock ready (address = tcp://127.0.0.1:28332)
2019-01-19T14:11:01Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-19T14:11:01Z zmq: Notifier pubrawtx ready (address = tcp://127.0.0.1:28332)

    This PR:

    2019-01-19T14:06:57Z zmq: version 4.3.1
2019-01-19T14:06:57Z zmq: Initialize notification interface
2019-01-19T14:06:57Z zmq: Outbound message high water mark for pubhashblock at tcp://127.0.0.1:28332 is 12345
2019-01-19T14:06:57Z zmq: Notifier pubhashblock ready (address = tcp://127.0.0.1:28332)
2019-01-19T14:06:57Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-19T14:06:57Z zmq: Outbound message high water mark for pubhashtx at tcp://127.0.0.1:28332 is 5000
2019-01-19T14:06:57Z zmq: Notifier pubhashtx ready (address = tcp://127.0.0.1:28332)
2019-01-19T14:06:57Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-19T14:06:57Z zmq: Outbound message high water mark for pubrawblock at tcp://127.0.0.1:28332 is 1000
2019-01-19T14:06:57Z zmq: Notifier pubrawblock ready (address = tcp://127.0.0.1:28332)
2019-01-19T14:06:57Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-19T14:06:57Z zmq: Outbound message high water mark for pubrawtx at tcp://127.0.0.1:28332 is 1000
2019-01-19T14:06:57Z zmq: Notifier pubrawtx ready (address = tcp://127.0.0.1:28332)
  2. zmq: log outbound message high water mark when reusing socket f1dc6932e9
  3. fanquake added the label RPC/REST/ZMQ on Jan 19, 2019
  4. fanquake added the label Utils/log/libs on Jan 19, 2019
  5. molxyz commented at 9:58 PM on January 19, 2019: none

    @fanquake How do you get the zmq log? I'm trying to run this PR but I don't see the log for zmq in my debug.log.

  6. fanquake commented at 12:19 AM on January 20, 2019: member

    @molxyz Run with -debug=zmq and you should see zmq related logs. I should have added that to the PR text.

  7. molxyz commented at 1:46 AM on January 20, 2019: none

    @fanquake Thank you! I should have figured that. This is great.

    2019-01-20T01:35:49Z zmq: version 4.2.5
2019-01-20T01:35:49Z zmq: Initialize notification interface
2019-01-20T01:35:49Z zmq: Outbound message high water mark for pubhashblock at tcp://127.0.0.1:28334 is 12345
2019-01-20T01:35:49Z zmq: Notifier pubhashblock ready (address = tcp://127.0.0.1:28334)
2019-01-20T01:35:49Z zmq: Outbound message high water mark for pubhashtx at tcp://127.0.0.1:28335 is 5000
2019-01-20T01:35:49Z zmq: Notifier pubhashtx ready (address = tcp://127.0.0.1:28335)
2019-01-20T01:35:49Z zmq: Outbound message high water mark for pubrawblock at tcp://127.0.0.1:28332 is 1000
2019-01-20T01:35:49Z zmq: Notifier pubrawblock ready (address = tcp://127.0.0.1:28332)
2019-01-20T01:35:49Z zmq: Outbound message high water mark for pubrawtx at tcp://127.0.0.1:28333 is 1000
2019-01-20T01:35:49Z zmq: Notifier pubrawtx ready (address = tcp://127.0.0.1:28333)

    Edit: Changed one of the ports to be the same like the other:

    2019-01-20T01:56:54Z zmq: version 4.2.5
2019-01-20T01:56:54Z zmq: Initialize notification interface
2019-01-20T01:56:54Z zmq: Outbound message high water mark for pubhashblock at tcp://127.0.0.1:28334 is 12345
2019-01-20T01:56:54Z zmq: Notifier pubhashblock ready (address = tcp://127.0.0.1:28334)
2019-01-20T01:56:54Z zmq: Reusing socket for address tcp://127.0.0.1:28334
2019-01-20T01:56:54Z zmq: Outbound message high water mark for pubhashtx at tcp://127.0.0.1:28334 is 5000
2019-01-20T01:56:54Z zmq: Notifier pubhashtx ready (address = tcp://127.0.0.1:28334)
2019-01-20T01:56:54Z zmq: Outbound message high water mark for pubrawblock at tcp://127.0.0.1:28332 is 1000
2019-01-20T01:56:54Z zmq: Notifier pubrawblock ready (address = tcp://127.0.0.1:28332)
2019-01-20T01:56:54Z zmq: Outbound message high water mark for pubrawtx at tcp://127.0.0.1:28333 is 1000
2019-01-20T01:56:54Z zmq: Notifier pubrawtx ready (address = tcp://127.0.0.1:28333)
  8. IlyasRidhuan commented at 1:13 PM on January 20, 2019: none

    tAck https://github.com/bitcoin/bitcoin/pull/15209/commits/f1dc6932e95fd29cbedfa5f013eca37ed91e12ed

    2019-01-20T13:22:25Z zmq: version 4.2.3
2019-01-20T13:22:25Z zmq: Initialize notification interface
2019-01-20T13:22:25Z zmq: Outbound message high water mark for pubhashblock at tcp://127.0.0.1:28332 is 12345
2019-01-20T13:22:25Z zmq: Notifier pubhashblock ready (address = tcp://127.0.0.1:28332)
2019-01-20T13:22:25Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-20T13:22:25Z zmq: Outbound message high water mark for pubhashtx at tcp://127.0.0.1:28332 is 5000
2019-01-20T13:22:25Z zmq: Notifier pubhashtx ready (address = tcp://127.0.0.1:28332)
2019-01-20T13:22:25Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-20T13:22:25Z zmq: Outbound message high water mark for pubrawblock at tcp://127.0.0.1:28332 is 1000
2019-01-20T13:22:25Z zmq: Notifier pubrawblock ready (address = tcp://127.0.0.1:28332)
2019-01-20T13:22:25Z zmq: Reusing socket for address tcp://127.0.0.1:28332
2019-01-20T13:22:25Z zmq: Outbound message high water mark for pubrawtx at tcp://127.0.0.1:28332 is 1000
2019-01-20T13:22:25Z zmq: Notifier pubrawtx ready (address = tcp://127.0.0.1:28332)
  9. laanwj commented at 4:18 PM on January 21, 2019: member

    utACK f1dc6932e95fd29cbedfa5f013eca37ed91e12ed

  10. laanwj merged this on Jan 21, 2019
  11. laanwj closed this on Jan 21, 2019
  12. laanwj referenced this in commit 1522079d54 on Jan 21, 2019
  13. fanquake deleted the branch on Feb 22, 2019
  14. jasonbcox referenced this in commit 6ad4149e5d on Sep 3, 2020
  15. PastaPastaPasta referenced this in commit 844c3a5e0a on Jun 26, 2021
  16. PastaPastaPasta referenced this in commit 625e4b9cbb on Jun 27, 2021
  17. PastaPastaPasta referenced this in commit 4a7e840a93 on Jun 28, 2021
  18. PastaPastaPasta referenced this in commit fd084d9bad on Jun 29, 2021
  19. dzutto referenced this in commit d65148909c on Sep 9, 2021
  20. UdjinM6 referenced this in commit 1dbf7b9d83 on Sep 9, 2021
  21. DrahtBot locked this on Dec 16, 2021
Contributors
fanquakemolxyzIlyasRidhuanlaanwj
Labels
RPC/REST/ZMQUtils/log/libs
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: 2026-04-13 15:15 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me