-
Notifications
You must be signed in to change notification settings - Fork 7
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
Connecting to windows remote machine with parallelly::makeClusterPSOCK hangs #96
Comments
Hi. as a starter, make sure you can do what's in Section 'Failing to set up remote workers' of https://parallelly.futureverse.org/reference/makeClusterPSOCK.html. Thanks for the video, but unfortunately, I cannot really see the text, because I've only got a 14-inch screen, so the fonts are too teeny. But, as a follow up on the above tests, look at the commands outputted when you do
but you'll get another |
Also, you could set |
Thanks for these @HenrikBengtsson I'll give them a quick try |
I did try the 'Failing to set up remote workers" section... I get the following debug output... I'll take a look into it
|
Can you paste in as plain text instead of screenshots? Then I can cut'n'paste from it |
Sure thing. Just let me know which ones you need.
|
AFAIU, you said:
workers, but then, in your last screenshot, you got an error:
So, maybe it cannot find And now I also see that you're setting So, retry with: cl <- parallelly::makeClusterPSOCK("10.0.44.224", user = "Julian",
rshopts = c("-i", ssh_private_key_file), dryrun = TRUE) and see if the proposed full call works, i.e. doesn't give that error. |
giving it a shot now... |
This is the output I get running your command
|
If any of them use parallelly, and not just parallel, let me know which they are, so I can make sure they're not giving incorrect instructions/suggestions. |
When I try with dryrun = FALSE
|
Also, happy to do a quick Zoom session -might be helpful to see what's going on in real time |
Try adding argument |
oh my! 😁
|
seems to have worked? Let me give it a quick test with the process I was using... |
Perfect! Works like a charm! |
… is needed if the remote machines run MS Windows [#96]
And just as a follow up... for setting up the Windows machine to access SSH connection using SSH keys... I used the following youtube video... This was really helpful as a fundamental step that I hadn't seen explained anywhere else. |
Happy to hear. Straight to the poolroom? :p PS. I've added an example for using remote MS Windows machines to https://parallelly.futureverse.org/reference/makeClusterPSOCK.html. |
Indeed. "How's the serenity" (knowing that it's finally working 😁👍
…On Sun, 22 Jan 2023, 4:38 pm Henrik Bengtsson, ***@***.***> wrote:
Happy to hear. Straight to the poolroom? :p
PS. I've added an example for using remote MS Windows machines to
https://parallelly.futureverse.org/reference/makeClusterPSOCK.html.
—
Reply to this email directly, view it on GitHub
<#96 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANPAGTGZ5LCZPY6UWEAJMCTWTTBUJANCNFSM6AAAAAAUCYLYMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I guess the world is not meant for 14-inch screens anymore 🤷 Oh well... so, getting up and running with SSH keys is tricky the first time, if you've never done it before, but as soon as you know how it should work, it's standard practice. It's been that way on Unix/Linux since ... the 90's. Now, the next step is to learn set more SSH defaults in |
Hi Henrik,
I made a blog post for parralelisation ...
For a developer to get the fundamentals working. Would love your feedback
if you had any free time.
***@***.***/how-to-do-hard-stuff-computationally-intensive-in-rstats-fa6d1b6213f
…On Mon, 23 Jan 2023, 3:56 am Henrik Bengtsson, ***@***.***> wrote:
Closed #96 <#96> as
completed.
—
Reply to this email directly, view it on GitHub
<#96 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANPAGTGMCA4MAPW73IJ3HH3WTVRCHANCNFSM6AAAAAAUCYLYMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
When I run the following code...
It hangs and doesn't end up connecting.
This is me connecting to another Windows 11 machine.
I have been able to SSH into it.
Any tips?
Here is a video of me troubleshooting with dryrun = TRUE
https://youtu.be/857DRD-k-DA
The text was updated successfully, but these errors were encountered: