You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nana-EC opened this issue
Oct 30, 2024
· 2 comments
Assignees
Labels
BugAn error that causes the feature to behave differently than what was expected based on design.P1High priority issue, which must be completed in the milestone otherwise the release is at risk.
When following the startup descriptions on how-to-set-up-a-hedera-local-node the step fails with [Hedera-Local-Node] ERROR (StartState) [✘] Something went wrong, while trying to connect to port 5600
In docker I then see that under the hedera-local-node group on 3 (hedera-explorer, havegd and relay-cache)of the 19 containers are running.
This is the full console stack
... % npm run start -- -d
> @hashgraph/[email protected] start
> npm run build && node ./build/index.js start -d
> @hashgraph/[email protected] build
> rimraf ./build && tsc
[Hedera-Local-Node] INFO (StateController) [✔︎] Starting start procedure!
[Hedera-Local-Node] INFO (InitState) ⏳ Making sure that Docker is started and it is correct version...
[Hedera-Local-Node] INFO (DockerService) ⏳ Checking docker compose version...
[Hedera-Local-Node] INFO (DockerService) ⏳ Checking docker resources...
[Hedera-Local-Node] INFO (InitState) ⏳ Setting configuration with latest images on host 127.0.0.1 with dev mode turned off using turbo mode in single node configuration...
[Hedera-Local-Node] INFO (InitState) [✔︎] Local Node Working directory set to /Users/nanaessilfie-conduah/Library/Application Support/hedera-local.
[Hedera-Local-Node] INFO (InitState) [✔︎] Hedera JSON-RPC Relay rate limits were disabled.
[Hedera-Local-Node] INFO (InitState) [✔︎] Needed environment variables were set for this configuration.
[Hedera-Local-Node] INFO (InitState) [✔︎] Needed bootsrap properties were set for this configuration.
[Hedera-Local-Node] INFO (InitState) [✔︎] Needed bootsrap properties were set for this configuration.
[Hedera-Local-Node] INFO (InitState) [✔︎] Needed mirror node properties were set for this configuration.
[Hedera-Local-Node] INFO (StartState) ⏳ Starting Hedera Local Node...
[Hedera-Local-Node] INFO (RecoveryState) ⏳ Starting Recovery State...
[Hedera-Local-Node] INFO (RecoveryState) ⏳ Trying to startup again...
[Hedera-Local-Node] INFO (StartState) ⏳ Detecting network...
[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
[Hedera-Local-Node] ERROR (StartState) [✘] Something went wrong, while trying to connect to port 5600
[Hedera-Local-Node] INFO (CleanUpState) ⏳ Initiating clean up procedure. Trying to revert unneeded changes to files...
[Hedera-Local-Node] INFO (CleanUpState) [✔︎] Clean up of consensus node properties finished.
[Hedera-Local-Node] INFO (CleanUpState) [✔︎] Clean up of mirror node properties finished.
Potentially related.
I saw the same behaviour when runnign npm run start -- -d --verbose=trace
In this case I saw
...
[Hedera-Local-Node] INFO (InitState) [✔︎] Local Node Working directory set to /Users/<localUserName>/Library/Application Support/hedera-local
...
[Hedera-Local-Node] DEBUG (DockerService) Error response from daemon: Mounts denied:
[Hedera-Local-Node] DEBUG (DockerService) The path /Users/<localUserName>/Library/Application Support/hedera-local/network-logs/node/accountBalances/balance0.0.3 is not shared from the host and is not known to Docker.
[Hedera-Local-Node] DEBUG (DockerService) You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.
[Hedera-Local-Node] DEBUG (DockerService) See https://docs.docker.com/desktop/settings/mac/#file-sharing for more info.
[Hedera-Local-Node] INFO (StartState) ⏳ Detecting network...
[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
[Hedera-Local-Node] ERROR (StartState) [✘] Something went wrong, while trying to connect to port 5600
When I Adding the local store dir to the Virtual file shares (Docker Settings -> Reosurces -> File Sharin) it fixed the problem.
However this isn't documented.
I'm using Docker desktop 4.35.0
Nana-EC
added
P1
High priority issue, which must be completed in the milestone otherwise the release is at risk.
Bug
An error that causes the feature to behave differently than what was expected based on design.
labels
Oct 30, 2024
Make sure all relevant Docker containers are running. You mentioned that there are 19 containers, of which only 3 are running. You can use the following command to view the status of all containers:
docker ps -a
If any containers are not running, try restarting them:
docker-compose up -d
But in fact, Docker is not very compatible with Mac.
You can try Servbay, which is more professional than Docker on Mac
BugAn error that causes the feature to behave differently than what was expected based on design.P1High priority issue, which must be completed in the milestone otherwise the release is at risk.
Description
When following the startup descriptions on how-to-set-up-a-hedera-local-node the step fails with
[Hedera-Local-Node] ERROR (StartState) [✘] Something went wrong, while trying to connect to port 5600
In docker I then see that under the
hedera-local-node
group on 3 (hedera-explorer, havegd and relay-cache)of the 19 containers are running.This is the full console stack
Steps to reproduce
FOllow how-to-set-up-a-hedera-local-node the steps
In a new folder
Additional context
No response
Hedera network
other
Version
v2.31.0
Operating system
macOS
The text was updated successfully, but these errors were encountered: