Blockhashes all zero duing syncing

[arnuschky]

monerod --version
Monero 'Oxygen Orion' (v0.17.1.7-release)

built https://github.com/vtnerd/motrix/commit/163ec8f04c15d6024d54c79f6d6c5b336ecb0446

[vtnerd]

Crap, its not fun or cool this way.

Was the progress meter still moving? Or did that stall too? The logic when handling a connection drop is a little tricky because ZMQ hides the actual connection attempts from the main API.

[arnuschky]

Progress was moving fine, so the connection was active.

[vtnerd]

Ok, I may have reproduced this locally. Check the ZMQ_PUB connection, which is separate from the RPC connection. monerod must be started with --zmq-pub and motrix must match this setting. If the PUB connection fails, it currently does so silently due to ZMQ behavior. The progress meter will still update periodically, because the code will probe the RPC channel if no pub-message was sent after 5 minutes.

I haven't found a quick way to debug whether this is the problem (without a patch), so apologies for the rather brief "check connection" response.

[vtnerd]

EDIT above: "if the PUB connection fails" ... a failed RPC connection is very obvious because nothing will work.

[vtnerd]

Or wait! Check the connection table from the OS. It should show two established connections - one for RPC and one for PUB.

[arnuschky]

Maybe I misunderstood how I start this.

I use monerod --zmq-pub tcp://127.0.0.1:18084 to start monerod on mainnet.

What should I call motrix with?

[vtnerd]

./motrix tcp://127.0.0.1:18084 tcp://127.0.0.1:18082 assuming both processes are on the same box. If they are on different boxes, then monerod is only listening for local connections.

[vtnerd]

Its probably synced by now so less fun :/ hopefully still useful.

[arnuschky]

Yes that works. Maybe add the command line parameters to the documentation or motrix itself?

It's really pretty, btw! Great job.

[vtnerd]

6 was opened to improve the error reporting.