-
Notifications
You must be signed in to change notification settings - Fork 53
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
BLRunner stuck on "OSError: Timed out trying to connect to 'inproc://172.17.0.2/10/1'" while running arboreto #48
Comments
Hi, |
I encountered the same problem. How did you solve it in the end? `distributed.comm.inproc - WARNING - Closing dangling queue in During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Hi,
I was trying to run grnbeeline/arboreto:base through BLRunner.py as the following command.
docker run --rm -v /home/abc/projects/Beeline:/data/ --expose=41269 grnbeeline/arboreto:base /bin/sh -c "time -v -o data/outputs/Synthetic/dyn-LI/dyn-LI-100-1/GENIE3/time.txt python runArboreto.py --algo=GENIE3 --inFile=data/inputs/Synthetic/dyn-LI/dyn-LI-100-1/GENIE3/ExpressionData.csv --outFile=data/outputs/Synthetic/dyn-LI/dyn-LI-100-1/GENIE3/outFile.txt "
However, an error occurred and the program stuck.
The error is not stable that there is a probability of the error in different places in multiple attempts.
Additionally, the containers are running under docker's bridge network.
The text was updated successfully, but these errors were encountered: