-
Notifications
You must be signed in to change notification settings - Fork 10
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
scvelo() "cannot open connection" #32
Comments
From the warnings, one of the calls has a 137 status, and this is ultimately causing the error. Some Googling suggests that this occurs when a Docker container runs out of memory, though I don't know enough about your system to know if this is applicable. |
I get the same error on a machine with 128 cores and 2 TB memory.
PREFIX=/home/rasmusr/.cache/basilisk/1.2.1/0 Package Planenvironment location: /home/rasmusr/.cache/basilisk/1.2.1/0 added / updated specs: The following NEW packages will be INSTALLED: _libgcc_mutex pkgs/main/linux-64::_libgcc_mutex-0.1-main Preparing transaction: ...working... done
Matrix products: default locale: attached base packages: other attached packages: loaded via a namespace (and not attached): |
Hm. I don't know why this happens. Suggest trying to run the minimal example in a fresh R session. # Copy-pasted from the error message above. Note the escape of the double quotes.
act.cmd <- ". '/d0/home/rasmusr/.cache/basilisk/1.2.1/0/etc/profile.d/conda.sh' && conda activate && /usr/lib/R/bin/Rscript --default-packages=NULL -e \"con <- socketConnection(port=11552, open='wb', blocking=TRUE);serialize(Sys.getenv(), con);close(con)\""
# Taken from the port above.
p <- 11552
soc <- serverSocket(p)
system(act.cmd, intern = TRUE)
listener <- socketAccept(soc, blocking = TRUE, open = "a+b")
activated <- unserialize(listener)
close(soc) Turning off |
Thanks for your suggestions. I ran it in a fresh R session using the paths from my error message. And I still get the same error "status 137".
|
Do you get more informative error messages if you remove Edit: After some more Googling, it turns out that 137 is a combination of the status codes 128 (fatal signal) and 9 (sigkill), see docs here. This is consistent with an examination of your error logs - see the Edit 2: I would be curious to see what happens for the simpler:
Or even just:
|
If I remove For the two other calls you suggested I get |
I have no idea what's going on here. My best guess is that your system is configured to kill any process that tries to connect to a port. While I could add a workaround... I don't want to, unless I get some more information about what's going wrong. My workaround won't solve the underlying port issue, which seems like it would break any socket-based parallelization via parallel. |
@shijianasdf As a general rule, if your situation is not obviously the same as an existing one, it is always better to create a new issue, so that users and developers can track and communicate on each issue separately. |
Thank you for your advice |
When I try to run the scvelo() function I get the following error message (see attached picture). I am pretty new to R and Python and would appreciate any help to solve that issue.
The text was updated successfully, but these errors were encountered: