Random errors creating txs with remote nodes [1 XMR]

[woodser]

Creating transactions when connected to remote nodes (especially xmr-node.cakewallet.com:18081 over Tor) sometimes produces random errors:

• no connection to daemon
• failed to get output distribution
• Failed to get height

This issue requests understanding and fixing these errors.

The errors tend to resolve by switching to a different node, switching to clearnet, using a local node, or trying again.

[github-actions[bot]]

There is a bounty on this issue, the amount is in the title. The reward will be awarded to the first person or group of people who resolves this issue.

If you are starting to work on this bounty, please write a comment, so that we can assign the issue to you. We expect contributors to provide a PR in a reasonable time frame or, in case of an extensive work, updates on their progresses. We will unassign the issue if we feel the assignee is not responsive or has abandoned the task.

Read the full conditions and details of our bounty system.

[nihilist001]

how about just making the haveno client retry a few times if it catches these errors ? idk if that'd be simple to implement or not

[woodser]

That's what we do now; most functions are retried 5 times for tolerance.

[boldsuck]

If it helps, there are several options to make Tor more talkative. (For debugging only, may provide sensitive information.)

Log debug file /var/log/tor/debug.log
SafeLogging 0
TestSocks 1

## SocksPort flag: ExtendedErrors
## Return extended error code in the SOCKS reply. So far, the possible errors are:
# X'F0' Onion Service Descriptor Can Not be Found
# X'F1' Onion Service Descriptor Is Invalid
# X'F2' Onion Service Introduction Failed
# X'F3' Onion Service Rendezvous Failed
# X'F4' Onion Service Missing Client Authorization
# X'F5' Onion Service Wrong Client Authorization
# X'F6' Onion Service Invalid Address
# X'F7' Onion Service Introduction Timed Out
SocksPort 9050 ExtendedErrors

MetricsPort 127.0.0.1:9035
MetricsPortPolicy accept 127.0.0.1

[KewbitXMR]

This doesn't just happen on Haveno, these happen everywhere including cake wallet and monero wallet GUI. I'm pretty sure this is to do with the network, tor or monerod, most likely monerod, I would say just throw catch and retry, and if it passes X number of times, switch to a different node and repeat....

[woodser]

Yeah that's what we do now; catch and retry, up to 5 times.