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

Socket files are not created #1124

Closed
dorin100 opened this issue Jun 2, 2020 · 4 comments
Closed

Socket files are not created #1124

dorin100 opened this issue Jun 2, 2020 · 4 comments
Assignees
Labels
bug Something isn't working cli revision is used to group all the Node CLI tickets

Comments

@dorin100
Copy link

dorin100 commented Jun 2, 2020

Summary
The socket file is not created and the below error can be seen into logs:

[ubuntu-4:cardano.node.ErrorPolicy:Warning:46] [2020-06-02 11:57:03.22 UTC] [String "ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError {errorType = MuxBearerClosed, errorMsg = \"<socket: 27> closed when reading data, waiting on next header True\", errorStack = []}))) 20s 20s",String "ErrorPolicyTrace",String "127.0.0.1:33483"]

The 3 nodes also do not seem to sync.

Steps to reproduce
Steps to reproduce the behavior:

  1. run the attached script (start_3node_cluster.sh) - it will generate all the files, folders and keys for all 3 nodes (2 BFT nodes and 1 Stake Pool)
  2. optionally you can rename the log files for each of the nodes (inside the configuration files inside each node's folder)
  3. start the nodes using the commands from the script's output
cardano-node run \
  --config                          cluster_3nodes/node-bft1/configuration.yaml \
  --topology                        cluster_3nodes/node-bft1/topology.json \
  --database-path                   cluster_3nodes/node-bft1/db \
  --socket-path                     cluster_3nodes/node-bft1/db/node.sock \
  --shelley-kes-key                 cluster_3nodes/node-bft1/kes.skey \
  --shelley-vrf-key                 cluster_3nodes/node-bft1/vrf.skey \
  --shelley-operational-certificate cluster_3nodes/node-bft1/node.cert \
  --port                            3001

cardano-node run \
  --config                          cluster_3nodes/node-bft2/configuration.yaml \
  --topology                        cluster_3nodes/node-bft2/topology.json \
  --database-path                   cluster_3nodes/node-bft2/db \
  --socket-path                     cluster_3nodes/node-bft2/db/node.sock \
  --shelley-kes-key                 cluster_3nodes/node-bft2/kes.skey \
  --shelley-vrf-key                 cluster_3nodes/node-bft2/vrf.skey \
  --shelley-operational-certificate cluster_3nodes/node-bft2/node.cert \
  --port                            3002

cardano-node run \
  --config                          cluster_3nodes/node-pool1/configuration.yaml \
  --topology                        cluster_3nodes/node-pool1/topology.json \
  --database-path                   cluster_3nodes/node-pool1/db \
  --socket-path                     cluster_3nodes/node-pool1/db/node.sock \
  --shelley-kes-key                 cluster_3nodes/node-pool1/kes.skey \
  --shelley-vrf-key                 cluster_3nodes/node-pool1/vrf.skey \
  --shelley-operational-certificate cluster_3nodes/node-pool1/node.cert \
  --port                            3003
  1. wait a couple of minutes and check the logs + if the node.sock file was created

Expected behavior
node.sock files should be created and all 3 local nodes should be in sync.

System info (please complete the following information):

  • OS: Ubuntu 20.04 LTS (GNU/Linux 5.4.0-28-generic x86_64)
  • branch: master
# git rev-parse --verify HEAD
b58154f1455e65324f7ddeb48dd9e2c7a53de325
  • Node version
# cardano-cli version
cardano-cli 1.12.0 - linux-x86_64 - ghc-8.6
git rev b58154f1455e65324f7ddeb48dd9e2c7a53de325

Screenshots and attachments

Additional context
I am trying to create and connect 3 local nodes.

@dorin100 dorin100 added bug Something isn't working Pioneer Issues related to the Pioneer F&F Testnet labels Jun 2, 2020
@oneEdoubleD
Copy link
Contributor

I've also seen this with Ubuntu 20.04 LTS however it was through WSL 2.

@kevinhammond kevinhammond added this to To do in CLI Revision via automation Jun 2, 2020
@kevinhammond kevinhammond added cli revision is used to group all the Node CLI tickets and removed Pioneer Issues related to the Pioneer F&F Testnet labels Jun 2, 2020
@kevinhammond kevinhammond added this to the S15 2020-06-18 milestone Jun 3, 2020
dcoutts added a commit that referenced this issue Jun 5, 2020
@dcoutts
Copy link
Contributor

dcoutts commented Jun 5, 2020

Fixed by #1145

@dorin100
Copy link
Author

dorin100 commented Jun 5, 2020

I confirm this is fixed on the latest master. Thank you!

@dorin100 dorin100 closed this as completed Jun 5, 2020
CLI Revision automation moved this from To do to Done Jun 5, 2020
@laplasz
Copy link
Contributor

laplasz commented Jan 4, 2021

Hi!

Still have this issue with version cardano-node 1.24.2

[dell:cardano.node.DnsSubscription:Notice:1926] [2021-01-04 14:49:42.53 UTC] [String "Connection Attempt Start, destination 18.192.31.165:29830",String "SubscriptionTrace",String "\"1.tcp.eu.ngrok.io\""]
[dell:cardano.node.DnsSubscription:Notice:1926] [2021-01-04 14:49:42.56 UTC] [String "Connection Attempt End, destination 18.192.31.165:29830 outcome: ConnectSuccessLast",String "SubscriptionTrace",String "\"1.tcp.eu.ngrok.io\""]
[dell:cardano.node.ChainDB:Notice:205] [2021-01-04 14:49:43.53 UTC] Chain extended, new tip: e7b15e622b91b1e02ab8242a5e738e681e57371617efd60319bf9f109053af63 at slot 16679425
[dell:cardano.node.DnsSubscription:Error:1926] [2021-01-04 14:49:43.79 UTC] [String "Application Exception: 18.192.31.165:29830 MuxError MuxBearerClosed \"<socket: 110> closed when reading data, waiting on next header True\"",String "SubscriptionTrace",String "\"1.tcp.eu.ngrok.io\""]
[dell:cardano.node.ErrorPolicy:Warning:253] [2021-01-04 14:49:43.79 UTC] [String "ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError MuxBearerClosed \"<socket: 110> closed when reading data, waiting on next header True\"))) 20s 20s",String "ErrorPolicyTrace",String "18.192.31.165:29830"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cli revision is used to group all the Node CLI tickets
Projects
No open projects
CLI Revision
  
Done
Development

No branches or pull requests

6 participants