Skip to content
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

[BUG] - ErrorPolicyUnhandledApplicationException when running cli commands on windows #1734

Closed
dorin100 opened this issue Aug 20, 2020 · 10 comments
Assignees
Labels
cli revision is used to group all the Node CLI tickets comp: networking networking Issues and PRs related to networking priority: low Would eventually require attention if time allows it. type: bug Something is not working user type: internal Created by an IOG employee

Comments

@dorin100
Copy link

Internal/Exernal
Internal if an IOHK staff member.

Summary
ErrorPolicyUnhandledApplicationException when running cli commands on windows

Steps to reproduce
Steps to reproduce the behavior:

  1. start node on windows using cardano-node.exe run --topology ./testnet-topology.json --database-path ./state --port 3001 --config ./testnet-config.json --socket-path \\.\pipe\cardano-node
  2. wait for the node to sync and get the tip using the bellow commands:
set CARDANO_NODE_SOCKET_PATH=\\.\pipe\cardano-node
cardano-cli.exe shelley query tip --testnet-magic 1097911063 
  1. Check the logs
←[31m[DESKTOP-:cardano.node.LocalErrorPolicy:Error:51]←[0m [2020-08-20 07:06:30.54 UTC] [String "ErrorPolicyUnhandledApplicationException (MuxError (MuxIOException withIODataPtr (readHandle): resource vanished (The pipe has been ended.)) \"(readHandle errored)\")",String "ErrorPolicyTrace",String "LocalAddress {getFilePath = \"\\\\\\\\.\\\\pipe\\\\cardano-node\"}"]

Expected behavior
No errors should be seen.

System info (please complete the following information):

  • OS: Windwos 10
  • Node version
>cardano-cli.exe --version
cardano-cli 1.19.0 - mingw32-x86_64 - ghc-8.6
git rev 4814003f14340d5a1fc02f3ac15437387a7ada9f

>cardano-cli.exe --version
cardano-cli 1.19.0 - mingw32-x86_64 - ghc-8.6
git rev 4814003f14340d5a1fc02f3ac15437387a7ada9f

Screenshots and attachments

Additional context
Add any other context about the problem here.

@dorin100 dorin100 added the bug Something isn't working label Aug 20, 2020
@kevinhammond
Copy link
Contributor

This has been reported to the team

@kevinhammond kevinhammond added the cli revision is used to group all the Node CLI tickets label Aug 25, 2020
@vix-io
Copy link
Contributor

vix-io commented Sep 23, 2020

hi @dorin100 @kevinhammond is this still relevant, does it happen consistently or random?

@vix-io vix-io assigned coot and unassigned Jimbo4350 and intricate Sep 23, 2020
@dcoutts
Copy link
Contributor

dcoutts commented Sep 23, 2020

I think the complaint here is not that the command fails, but that the node logs reports the successful disconnection of the client as an unhandled mux error.

ErrorPolicyUnhandledApplicationException
  (MuxError (MuxIOException withIODataPtr (readHandle):
  resource vanished (The pipe has been ended.)) \"(readHandle errored)\")

The mux error types should not be classified as an unhandled exception.

@coot
Copy link
Contributor

coot commented Sep 24, 2020

I believe this will be solved by the p2p node we are working in the networking team. There we classifies errors better: each exception either kills the node or just brings connection down, there's no third option (unhandled exceptions). We will still need to tune logging.

@McCalm
Copy link

McCalm commented Mar 4, 2021

These error messages are still displayed in all logs on my different servers (Windows 10; current version) in the Daedalus Mainnet Software v3.3.2 #16919. It is interesting that this message always appears after the information "Switched to a fork, new tip:". I leave everything else to you programmer of the source code, maybe this info will be helpful for you.

This error message ALWAYS appears and only at this point after the information "switched to a fork...".

Greetings.

[...]

Chain extended, new tip: 5761....e251 at slot 23307720
cardano.node.ChainDB:Info:25]�[0m [2021-03-04 16:06:54.52 UTC] Block fits onto some fork: e7913....e5fae at slot 23307720
cardano.node.ChainDB:Info:25]�[0m [2021-03-04 16:06:54.53 UTC] Valid candidate e7913....e5fae at slot 23307720
cardano.node.ChainDB:Notice:25]�[0m [2021-03-04 16:06:54.53 UTC] Switched to a fork, new tip: e7913....e5fae at slot 23307720
cardano.node.LocalErrorPolicy:Error:46]�[0m [2021-03-04 16:06:54.53 UTC] IP LocalAddress "\\.\pipe\cardano-node-mainnet" ErrorPolicyUnhandledApplicationException (MuxError (MuxIOException withIODataPtr (readHandle): resource vanished (Die Pipe wurde beendet.)) "(readHandle errored)")
cardano.node.LocalErrorPolicy:Error:46]�[0m [2021-03-04 16:06:54.53 UTC] IP LocalAddress "\\.\pipe\cardano-node-mainnet" ErrorPolicyUnhandledApplicationException (MuxError (MuxIOException withIODataPtr (readHandle): resource vanished (Die Pipe wurde beendet.)) "(readHandle errored)")
cardano.node.ChainDB:Notice:25]�[0m [2021-03-04 16:07:03.19 UTC] Chain extended, new tip:

[...]

@ggcaponetto
Copy link

i noticed the same on ubuntu focal running version 1.29.0

[2b17b884:cardano.node.ChainDB:Info:36] [2021-09-25 06:48:08.61 UTC] Block fits onto some fork: b607a000d17252a753b7efb635c6cf2ea4ce2ca283e8a11a222caec09cd01aef at slot 40986196

[2b17b884:cardano.node.ChainDB:Info:36] [2021-09-25 06:48:08.96 UTC] Valid candidate b607a000d17252a753b7efb635c6cf2ea4ce2ca283e8a11a222caec09cd01aef at slot 40986196

[2b17b884:cardano.node.ChainDB:Notice:36] [2021-09-25 06:48:08.96 UTC] Switched to a fork, new tip: b607a000d17252a753b7efb635c6cf2ea4ce2ca283e8a11a222caec09cd01aef at slot 40986196

[2b17b884:cardano.node.LocalErrorPolicy:Error:67] [2021-09-25 06:48:09.98 UTC] IP LocalAddress "" ErrorPolicyUnhandledApplicationException (MuxError MuxBearerClosed "<socket: 40> closed when reading data, waiting on next header True")

[2b17b884:cardano.node.ChainDB:Notice:36] [2021-09-25 06:48:18.35 UTC] Chain extended, new tip: 58fd5dee445a98c78be0a949829b5a60de2d8a374d958fea72419e3b7d320651 at slot 40986205

[2b17b884:cardano.node.ChainDB:Notice:36] [2021-09-25 06:48:41.66 UTC] Chain extended, new tip: 903734506b82bf3fa1fdd2c3f8f809ae583b183f270b412d4a31c1838f5c8f3a at slot 40986229

@coot
Copy link
Contributor

coot commented Sep 26, 2021

Thanks for reporting. As I mentioned, this will be fixed with p2p release.

@coot coot added logging and monitoring networking Issues and PRs related to networking and removed bug Something isn't working labels Sep 26, 2021
@Plamen5kov
Copy link

hey @coot thank you for the help,
I'm having the same issues, I was just wandering what is a p2p release and do you have any idea on when that release is coming or where I could follow the progress of it?

@coot
Copy link
Contributor

coot commented Jan 27, 2022

You can follow progress on the p2p here.

@deepfire deepfire moved this to Backlog in Performance & Tracing Aug 19, 2022
@dorin100 dorin100 added type: bug Something is not working user type: internal Created by an IOG employee priority: low Would eventually require attention if time allows it. comp: networking labels Oct 21, 2022
@Jimbo4350
Copy link
Contributor

Closing this. If this is still relevant please re-open.

Repository owner moved this from Backlog to Done in Performance & Tracing Oct 27, 2022
@Jimbo4350 Jimbo4350 moved this to Done in Ouroboros Network Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli revision is used to group all the Node CLI tickets comp: networking networking Issues and PRs related to networking priority: low Would eventually require attention if time allows it. type: bug Something is not working user type: internal Created by an IOG employee
Projects
None yet
Development

No branches or pull requests