bcgov / von-network

A portable development level Indy Node network.
Apache License 2.0
155 stars 186 forks source link

The network is not starting #129

Open HarshMultani opened 3 years ago

HarshMultani commented 3 years ago

I have followed all the steps to spin up the network locally using docker in a linux environment. But when I run the command sudo ./manage start

It gives the error - An Http request took too long to complete - consider setting COMPOSE_HTTP_TIMEOUT to a higher value.

Can someone please give a workaround over this quickly

WadeBarnes commented 3 years ago

Can you confirm the steps you performed were:

./manage build
./manage start

Are there any other logs you can provide?

HarshMultani commented 3 years ago

Yes I have run those commands :-

This is my run :-

harsh@harsh-VirtualBox:~/Desktop/von_network/von-network$ sudo ./manage build [sudo] password for harsh: Sending build context to Docker daemon 316.4kB Step 1/9 : FROM bcgovimages/von-image:node-1.12-3 ---> 860f94308216 Step 2/9 : ENV LOG_LEVEL ${LOG_LEVEL:-info} ---> Using cache ---> 887a3d8edaa0 Step 3/9 : ENV RUST_LOG ${RUST_LOG:-warning} ---> Using cache ---> c2ebb428d76d Step 4/9 : ADD config ./config ---> Using cache ---> 1a4152f13cc3 Step 5/9 : ADD server/requirements.txt server/ ---> Using cache ---> 5cd5883d22bb Step 6/9 : RUN pip install --no-cache-dir -r server/requirements.txt ---> Using cache ---> 888bd40c18be Step 7/9 : ADD --chown=indy:indy indy_config.py /etc/indy/ ---> Using cache ---> 6a13e89d57e5 Step 8/9 : ADD --chown=indy:indy . $HOME ---> Using cache ---> f2978e6ecf79 Step 9/9 : RUN mkdir -p $HOME/cli-scripts && chmod -R ug+rw $HOME/cli-scripts ---> Using cache ---> 8247c03ab075 Successfully built 8247c03ab075 Successfully tagged von-network-base:latest harsh@harsh-VirtualBox:~/Desktop/von_network/von-network$ sudo ./manage start --logs Starting von_node4_1 ... Starting von_node2_1 ... Starting von_node1_1 ... Starting von_node3_1 ... Starting von_webserver_1 ...

ERROR: for von_node1_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for von_webserver_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for von_node3_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for von_node2_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for von_node4_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for node1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for webserver UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for node3 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for node2 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for node4 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60) ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60). harsh@harsh-VirtualBox:~/Desktop/von_network/von-network$

WadeBarnes commented 3 years ago

What is the output of docker ps? It looks like a docker networking issue.

HarshMultani commented 3 years ago

Hi,

I have reset the value of COMPOSE_HTTP_TIMEOUT to 200 and it works now. Now the server is up and running. But when I am going to localhost:9000 - It is displaying that "Error initializing pool ledger" Any help on this?

WadeBarnes commented 3 years ago

It can take a minute or two for the nodes to spin up and the ledger browser to connect. Things appear to be slower on your machine so it may take a bit longer.

WadeBarnes commented 3 years ago

If you continue to have that issue you can try running ./manage down to reset the von-network instance:

./manage down
./manage start
HarshMultani commented 3 years ago

Now, I have shifted everything and moved from linux to windows 10. I have then download docker-toolbox Then when I am running the command ./manage start .

It gives No module name server.server von_webserver_1 exited with code 1.

Any inputs on this ?

WadeBarnes commented 3 years ago

The recommended approach on Windows 10 is to use Docker Desktop. It supports either Hyper-V or WSL-2 based docker containers. I'm on Windows 10 and I use von-network a lot. I seem to recall some issues with docker-toolbox. Also that particular error message makes me suspect you are not using the latest version of the code. I recall having a similar error at one time, but we resolved that issue a long time ago.

WadeBarnes commented 3 years ago

I think you're running into a volume mounting issue. Try the solution here; https://github.com/bcgov/von-network/issues/107#issuecomment-601896309

HarshMultani commented 3 years ago

Yes, thanks Wade,

Also wanted to add - as I am using docker toolbox so I have to use it's IP - as Stephen has commented here [ https://github.com/bcgov/von-network/issues/107#issuecomment-601896686 ]

akshaykurhekar commented 2 years ago

hi, if you are getting "Error initializing pool ledger" on localhost 9000 for von-network try this.

if the network is running stop it ./manage down

and then

./manage rebuild ./manage start

this works for me

Screenshot from 2022-05-23 13-38-52

andersonphiri commented 1 year ago

I had the same problem, My Environment: windows 11 Pro, and running on Ubuntu 22.4 wsl 2.0 with docker desktop running with wsl backend: all nodes exiting with code 1 and the fix is either : change docker compose volume mappings for nodes to start with ~/your/path/node-number

OR download the releases and unzip and run ./manage rebuild && ./manage start V1.7.2 is working in my environment with no issues at all

von-network