Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ZMQ died silently
See original GitHub issueIssue Description
ZMQ silently died again without signal about disconnecting with node. Last signal I got on my node was from
2021-08-02 10:27:36,964 INFO f.a.e.b.b.zmq.ZMQActor - connected to tcp://192.168.2.7:29000
then I used it for a while and on 6th Aug node didn’t signal about ZMQ disruptions while Watchdog indicated eclipsing.
2021-08-06 12:39:20,703 WARN f.a.e.b.w.BlockchainWatchdog - blockcypher.com: we are 10 blocks late: we may be eclipsed from the bitcoin network
2021-08-06 12:54:10,281 WARN f.a.e.b.w.BlockchainWatchdog - blockstream.info: we are 13 blocks late: we may be eclipsed from the bitcoin network
2021-08-06 12:54:10,998 WARN f.a.e.b.w.BlockchainWatchdog - mempool.space: we are 13 blocks late: we may be eclipsed from the bitcoin network
2021-08-06 12:54:11,860 WARN f.a.e.b.w.BlockchainWatchdog - bitcoinheaders.net: we are 9 blocks late: we may be eclipsed from the bitcoin network
2021-08-06 12:54:20,448 WARN f.a.e.b.w.BlockchainWatchdog - blockcypher.com: we are 13 blocks late: we may be eclipsed from the bitcoin network
Restarting BITCOIND didn’t help that’s why I think ZMQ actor died.
version 0.6.2-SNAPSHOT-cafaeed
Issue Analytics
- State:
- Created 2 years ago
- Comments:35 (35 by maintainers)
Top Results From Across the Web
Reaper thread silently dies when terminate is called ... - GitHub
This condition causes an IOException during the reaping process, which results in the reaper thread silently dying. Once the reaper thread has ...
Read more >Chapter 4 - Reliable Request-Reply Patterns - ZeroMQ guide
When a recipient knows the other side died, it can for example switch over to a backup route. If we use a TCP...
Read more >Developers - Reaper thread silently dies when terminate is called ...
Reaper thread silently dies when terminate is called when socket under heavy load. zeromq. 03 March 2016 Posted by ppridge.
Read more >ZeroMQ 'Restart' if no reply was recieved - Stack Overflow
In distributed-system any problem cease to be a just-local isuue, so unhandled exceptions, fallen into a silent death of some agent will ...
Read more >Designing Reliability - ZeroMQ [Book] - O'Reilly
If the server dies while processing a request, the client can figure that out because it won't get an answer back. Then it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s also a good point, we only need an event and we’re only using the block hash (and just for logging purposes). We initially scanned the actual block, but that changed a while ago. I’ll prototype migrating to block hash to save bandwidth.
Btw, is block itself needed or do we only need a new block event (in which case block hash would suffice)?
Looking at
ZmqWatcherand I don’t see stuff like scanning block contents, rather everything seems to be done by calling bitcoind api. Am I missing something?If not then switching to block hashes can save traffic for setups with remote bitcoind.