List-notes-by-pubkey problems

General
1

Since the recent (last two or three days) code / network improvements, things have seemed a lot smoother for my two miners (M4 Pro and 64GB RAM), in the sense that both are now staying up to date with the network. However, I’m no longer able (using either miner’s .socket/nockchain_npc.sock as --nockchain-socket) to successfully use the wallet commands for listing notes by pubkey. It hangs for a few minutes at wallet: warning: debug printing may expose sensitive information, then prints "list-notes-by-pubkey" and "list-notes-by-pubkey": [my pub key] five or six times, then a long error trace. Any recommended remedies? (I should mention that these exact commands were working in the past, prior to the recent code updates.)

2

our wallet guy is working to speed this up as we speak.

3

Still getting the same basic error even after pulling down and re-making/building everything with the newest code. Also, the miner logs are absolutely strewn with “failed to dial address” errors, many of which contain RFC 1918 addresses. Not sure how those are leaking into your peer lists.

4

Example:

W (20:41:35) nc: Error making request to peer 12D3KooWRboLFNh3h5yEy1mbxg3h2J1AZqrYgCpx211rqRTeQWgK: Eof { name: "enum", expect: Small(1) }
W (20:41:35) nc: Error making request to peer 12D3KooWF1wNCpR8Njo5zQcbDrjYthYqVf1Y44maiJkvd8jyWomj: Eof { name: "enum", expect: Small(1) }
W (20:41:35) nc: Error making request to peer 12D3KooWHqeJaG91f17fpj1KgGszBg8WFqyL63ZDdQkXpLY2oiC3: Eof { name: "enum", expect: Small(1) }
W (20:41:35) nc: Error making request to peer 12D3KooWQjvRag8dpnPzVkGmiymj9TMPErBXZCLp2mJa9exXMvCW: Eof { name: "enum", expect: Small(1) }
W (20:41:35) nc: Error making request to peer 12D3KooWSk8GqKHFnTu5o4qRX5YeTkRLAo439cgwmexWEYT3Rg63: Eof { name: "enum", expect: Small(1) }
W (20:41:35) nc: Error making request to peer 12D3KooWSsTm21UAxD7CBowqy2AevomTgbuPi95zmrVcuydvHfr2: Eof { name: "enum", expect: Small(1) }
W (20:41:35) nc: Error making request to peer 12D3KooWQSHhfSumP2tGAUXPhdwk4apoEaisDEtBVpvKSeKyn1AN: Eof { name: "enum", expect: Small(1) }
W (20:41:40) nc: Failed to dial address /ip4/192.168.7.50/udp/33485/quic-v1/p2p/12D3KooWAFNC8Jwqn7Do6nNWsZYRRjaTbpMkrCfdJYDcuYZgH3t6: 
W (20:41:41) nc: Failed to dial address /ip4/192.168.50.1/udp/3128/quic-v1/p2p/12D3KooWJTbMGSGVzGC1VwMuFsEiQdZFbaB4T2CSH3iKErkMFKFQ: 
W (20:41:45) nc: Failed to dial address /ip4/192.200.113.138/udp/3192/quic-v1/p2p/12D3KooWGK8dyJbfCCjgiMQeqhwTJuCkF9Vpku9ZbSirQ8mNf9Ys: 
W (20:41:50) nc: Failed to dial address /ip4/127.0.0.1/udp/3588/quic-v1/p2p/12D3KooWHL2R7ToTsHScvm62ft1PBPTsKLVDiztL9cmw8VAnfjs6: 
W (20:41:51) nc: Failed to dial address /ip4/192.200.113.138/udp/3028/quic-v1/p2p/12D3KooWP3bPqRShxNbDAVPKa38nsZQMBJscMisnmZSNP63UYwDm:
5

can you try running the wallet with --new? make sure to backup your keys first with --export-keys, you can import them again with --import-keys.

1 Like
6

Thanks, that seems to have worked! While I’m curious what could have been an issue with the wallet’s state, the most important thing is that —new and reimporting the keys cleared things up.

2 Likes