Closed aronneewart closed 2 years ago
@aronneewart thanks for all the detailed info. Seems like the Ouroboros handshake is failing. Oura asks for V10 of the Node-2-Client mini-protocols (a requirement which might be too strict I'm afraid).
Can you share the cardano-node / Daedalus version you're using?
How could I forgot that info!
Daedalus 4.6.0
Linux build 20052, Cardano Node 1.30.1, Cardano Wallet 2021.11.11
cardano-node 1.30.1 - linux-x86_64 - ghc-8.10
git rev 0fb43f4e3da8b225f4f86557aed90a183981a64f
@aronneewart I was able to reproduce with version 1.30 of cardano-node.
The node-to-client logic on Oura uses a local-state query to fetch the current tip of the node. AFAIK, this query was introduced in NodeToClientV_10
, which I believe it ships in cardano-node 1.31.
To fix the issue, I refactored the tip-fetching logic to match the one we use in the node-to-node connection (which uses a hardcoded intersect request just to get the tip response back).
This fix is being shipped in Oura release 0.3.4
My God they're already at 1.32.1! Time truly flies quicker under the pandemic. Thanks so much for reviewing the issues!
Running both Daedalus and
cardano-node
(standalone) showed the very same results:Running with
--bearer unix
threw the same error in all scenariosand
on
cardano-node
in parallel. Also, to ensure the existence and functionality of the socket file, I connected to it successfully withcardano-wallet serve --node-socket /home/aron/.local/share/Daedalus/mainnet/cardano-node.socket --mainnet
On the other hand tcp worked like a charm :heart:
Environment: Arch Linux 5.15.7-arch1-1 x86_64 GNU/Linux