-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discovery error with peer: NBitcoin.Protocol.NetworkAddress OperationCanceledException: The operation was canceled #2
Comments
Thanks. We're overhauling the network code, which should fix this bug. We've restarted the seed peers so you should be able to connect in the mean time. |
got the same issue here |
The app started back to connect |
got the same issue here |
here is the same error |
The app could connect to peer now, though it still generated an error msg beforehand: |
I notify when you open the app it's allwayse fail to get the connection. But after a time X it will successed connect |
@pw96pw96pw96 - new binaries are available for download which should fix the issue you encountered |
@Douvi this is not actually a bug or an error, it's just that the trace shouldn't be printing that. it's printed when a connection cant be established with a peer that's listed in the node's address list |
@UrbanSharon - It will be helpful if instructions on how to build and run from source could be given. Anyway, thank you for fixing the issue. |
@UrbanSharon I sent some Zen via the faucet into address 14eh93uk/Nfogl/NiyHVpwzxCXPz6Z8kv/CRMFVzaCr0=. But when I opened the wallet/portfolio, it says "Discovering peers: 0%" See screenshot. My node started via mono zen.exe -m is running fine. |
@UrbanSharon After leaving the wallet open for a long time, it can show the balance now. I guess it was because the wallet was downloading all the blocks. Issue resolved. Thx. |
following the instructions for OSX (https://www.zenprotocol.com/alpha).
Full Stack:
Network(E) Discovery error with peer: NBitcoin.Protocol.NetworkAddress OperationCanceledException: The operation was canceled. at System.Collections.Concurrent.BlockingCollection
1[T].TryTakeWithNoTimeValidation (T& item, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken, System.Threading.CancellationTokenSource combinedTokenSource) [0x0008e] in <5afdc70d980c4033b3878286f754d091>:0 at System.Collections.Concurrent.BlockingCollection
1[T].TryTake (T& item, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00006] in <5afdc70d980c4033b3878286f754d091>:0at System.Collections.Concurrent.BlockingCollection
1[T].Take (System.Threading.CancellationToken cancellationToken) [0x00000] in <5afdc70d980c4033b3878286f754d091>:0 at NBitcoin.Protocol.PollMessageListener
1[T].ReceiveMessage (System.Threading.CancellationToken cancellationToken) [0x00006] in :0at NBitcoin.Protocol.NodeListener.ReceivePayload[TPayload] (System.Threading.CancellationToken cancellationToken) [0x000d1] in :0
at NBitcoin.Protocol.Node.VersionHandshake (NBitcoin.Protocol.NodeRequirement requirements, System.Threading.CancellationToken cancellationToken) [0x00044] in :0
at NBitcoin.Protocol.Node.VersionHandshake (System.Threading.CancellationToken cancellationToken) [0x00000] in :0
at NBitcoin.Protocol.AddressManager+<>c__DisplayClass70_0.b__1 (NBitcoin.Protocol.NetworkAddress p) [0x00086] in :0
The text was updated successfully, but these errors were encountered: