Re: [julia-users] Adding remote workers on windows
> > I meant the remote machine/network may be firewalled to only accept > incoming ssh, http and other known ports. OK sorry. By now you can probably guess I don't really understand networking. Anyway I turned off the remote firewall entirely, and addprocs() successfully added remote worker, Yippee! Then I re-enabled the remote firewall and confirmed ssh server was enabled through the firewall. But now addprocs() failed with wait error as before. Definitely something to do with firewall blocking but seemingly not ssh server. What to do? After much playing around, and for some unknown but inspired reason (well, for me anyway), I decided to add Julia to allowed "apps" and Presto it worked! Not really sure why Julia wasn't in already in allowed list. I didn't need do this on another network where it just worked out of the box. In any case, for completeness and so it might help anyone else, here's what I did: Control Panel Windows Firewall Allow an app or feature through Windows Firewall (since Julia was not already in list) Allow another app Select Julia from list of applications, and click Add. On Tuesday, September 8, 2015 at 1:27:44 PM UTC+10, Amit Murthy wrote: > I meant the remote machine/network may be firewalled to only accept > incoming ssh, http and other known ports. > > On Tue, Sep 8, 2015 at 5:49 AM, greg_plowman via julia-users < > julia...@googlegroups.com > wrote: > > >> Is port 9009 open on the remote machine? You could try with "tunnel=true" >>> if it is not open. >> >> >> I think so. >> After running addprocs() and before the wait error, netstat on the >> remote machine outputs the following: >> >> C:\Users\Greg>netstat -an >> Active Connections >> Proto Local Address Foreign AddressState >> TCP0.0.0.0:22 0.0.0.0:0 LISTENING >> TCP0.0.0.0:1350.0.0.0:0 LISTENING >> TCP0.0.0.0:4450.0.0.0:0 LISTENING >> TCP0.0.0.0:5540.0.0.0:0 LISTENING >> TCP0.0.0.0:2869 0.0.0.0:0 LISTENING >> TCP0.0.0.0:3389 0.0.0.0:0 LISTENING >> TCP0.0.0.0:5357 0.0.0.0:0 LISTENING >> TCP0.0.0.0:8092 0.0.0.0:0 LISTENING >> TCP0.0.0.0:9009 0.0.0.0:0 LISTENING >> TCP0.0.0.0:10243 0.0.0.0:0 LISTENING >> TCP0.0.0.0:26143 0.0.0.0:0 LISTENING >> TCP0.0.0.0:47984 0.0.0.0:0 LISTENING >> ... >> >> When the remote session terminates, the 9009 entry is missing from >> netstat output. >> >> On Monday, September 7, 2015 at 9:24:38 PM UTC+10, Amit Murthy wrote: >> >>> Is port 9009 open on the remote machine? You could try with >>> "tunnel=true" if it is not open. >>> >>> On Mon, Sep 7, 2015 at 4:32 PM, Greg Plowman >>> wrote: >>> >>> Hi, I'm trying to use addprocs() to add remote workers on another windows machine. I'm using a ssh server for windows (Bitvise) with a modified Cluster Manager, and have successfully used this method in another environment. So I know that it works, although one difference is Window 7 (works) vs Windows 8.1 (does not work), but I don't think this should be problem. Now, I don't expect anyone to troubleshoot my particular setup / environment / customisation. Rather I was hoping for some high level help with further diagnosis. I can confirm that the windows command to launch the remote worker is executed, and the remote machine receives a connection and then successful login. The remote ssh server shows a successful connection and login, and windows Task Manager shows a Julia process has started. Then the following error occurs on the local machine, after which the remote session is terminated. Error evaluating c:\Users\Greg\Julia6\src\Launcher.jl: connect: connection timed out (ETIMEDOUT) in wait at task.jl:284 in wait at task.jl:194 in stream_wait at stream.jl:263 in wait_connected at stream.jl:301 in Worker at multi.jl:113 in create_worker at multi.jl:1064 in start_cluster_workers at multi.jl:1028 I guess my first question is which side (local or remote) is failing. It seems to me that the local Julia process is waiting for some confirmation of connection? Does that sound right? If so, are there any suggestions on how to further diagnose problem. When the ssh command to start a remote Julia worker is executed from the windows command line, I get the following: julia_worker:9009#192.168.1.107 Then after about 60s: Master process (id 1) could not connect within 60.0 seconds. exiting. Presumably this is the expected behaviour, si
Re: [julia-users] Adding remote workers on windows
I meant the remote machine/network may be firewalled to only accept incoming ssh, http and other known ports. On Tue, Sep 8, 2015 at 5:49 AM, greg_plowman via julia-users < julia-users@googlegroups.com> wrote: > Is port 9009 open on the remote machine? You could try with "tunnel=true" >> if it is not open. > > > I think so. > After running addprocs() and before the wait error, netstat on the remote > machine outputs the following: > > C:\Users\Greg>netstat -an > Active Connections > Proto Local Address Foreign AddressState > TCP0.0.0.0:22 0.0.0.0:0 LISTENING > TCP0.0.0.0:1350.0.0.0:0 LISTENING > TCP0.0.0.0:4450.0.0.0:0 LISTENING > TCP0.0.0.0:5540.0.0.0:0 LISTENING > TCP0.0.0.0:2869 0.0.0.0:0 LISTENING > TCP0.0.0.0:3389 0.0.0.0:0 LISTENING > TCP0.0.0.0:5357 0.0.0.0:0 LISTENING > TCP0.0.0.0:8092 0.0.0.0:0 LISTENING > TCP0.0.0.0:9009 0.0.0.0:0 LISTENING > TCP0.0.0.0:10243 0.0.0.0:0 LISTENING > TCP0.0.0.0:26143 0.0.0.0:0 LISTENING > TCP0.0.0.0:47984 0.0.0.0:0 LISTENING > ... > > When the remote session terminates, the 9009 entry is missing from netstat > output. > > > On Monday, September 7, 2015 at 9:24:38 PM UTC+10, Amit Murthy wrote: > >> Is port 9009 open on the remote machine? You could try with "tunnel=true" >> if it is not open. >> >> On Mon, Sep 7, 2015 at 4:32 PM, Greg Plowman wrote: >> >>> Hi, >>> >>> I'm trying to use addprocs() to add remote workers on another windows >>> machine. >>> >>> I'm using a ssh server for windows (Bitvise) with a modified Cluster >>> Manager, and have successfully used this method in another environment. >>> So I know that it works, although one difference is Window 7 (works) vs >>> Windows 8.1 (does not work), but I don't think this should be problem. >>> >>> Now, I don't expect anyone to troubleshoot my particular setup / >>> environment / customisation. >>> Rather I was hoping for some high level help with further diagnosis. >>> >>> I can confirm that the windows command to launch the remote worker is >>> executed, and the remote machine receives a connection and then successful >>> login. >>> The remote ssh server shows a successful connection and login, and >>> windows Task Manager shows a Julia process has started. >>> Then the following error occurs on the local machine, after which the >>> remote session is terminated. >>> >>> Error evaluating c:\Users\Greg\Julia6\src\Launcher.jl: >>> connect: connection timed out (ETIMEDOUT) >>> in wait at task.jl:284 >>> in wait at task.jl:194 >>> in stream_wait at stream.jl:263 >>> in wait_connected at stream.jl:301 >>> in Worker at multi.jl:113 >>> in create_worker at multi.jl:1064 >>> in start_cluster_workers at multi.jl:1028 >>> >>> I guess my first question is which side (local or remote) is failing. >>> It seems to me that the local Julia process is waiting for some >>> confirmation of connection? Does that sound right? >>> If so, are there any suggestions on how to further diagnose problem. >>> >>> When the ssh command to start a remote Julia worker is executed from the >>> windows command line, I get the following: >>> julia_worker:9009#192.168.1.107 >>> >>> Then after about 60s: >>> Master process (id 1) could not connect within 60.0 seconds. >>> exiting. >>> >>> Presumably this is the expected behaviour, since the remote worker >>> process is not communicating with master Julia process? >>> >>> Maybe the remote Julia.exe command is not receiving the --worker >>> argument properly? >>> >>> As I said, my method works in another environment (which incidentally >>> seems like magic to me). >>> I'm not really sure what is different here. >>> So any suggestions would be appreciated. >>> >>> Thanks, Greg >>> >> >>
Re: [julia-users] Adding remote workers on windows
> > Is port 9009 open on the remote machine? You could try with "tunnel=true" > if it is not open. I think so. After running addprocs() and before the wait error, netstat on the remote machine outputs the following: C:\Users\Greg>netstat -an Active Connections Proto Local Address Foreign AddressState TCP0.0.0.0:22 0.0.0.0:0 LISTENING TCP0.0.0.0:1350.0.0.0:0 LISTENING TCP0.0.0.0:4450.0.0.0:0 LISTENING TCP0.0.0.0:5540.0.0.0:0 LISTENING TCP0.0.0.0:2869 0.0.0.0:0 LISTENING TCP0.0.0.0:3389 0.0.0.0:0 LISTENING TCP0.0.0.0:5357 0.0.0.0:0 LISTENING TCP0.0.0.0:8092 0.0.0.0:0 LISTENING TCP0.0.0.0:9009 0.0.0.0:0 LISTENING TCP0.0.0.0:10243 0.0.0.0:0 LISTENING TCP0.0.0.0:26143 0.0.0.0:0 LISTENING TCP0.0.0.0:47984 0.0.0.0:0 LISTENING ... When the remote session terminates, the 9009 entry is missing from netstat output. On Monday, September 7, 2015 at 9:24:38 PM UTC+10, Amit Murthy wrote: > Is port 9009 open on the remote machine? You could try with "tunnel=true" > if it is not open. > > On Mon, Sep 7, 2015 at 4:32 PM, Greg Plowman > wrote: > >> Hi, >> >> I'm trying to use addprocs() to add remote workers on another windows >> machine. >> >> I'm using a ssh server for windows (Bitvise) with a modified Cluster >> Manager, and have successfully used this method in another environment. >> So I know that it works, although one difference is Window 7 (works) vs >> Windows 8.1 (does not work), but I don't think this should be problem. >> >> Now, I don't expect anyone to troubleshoot my particular setup / >> environment / customisation. >> Rather I was hoping for some high level help with further diagnosis. >> >> I can confirm that the windows command to launch the remote worker is >> executed, and the remote machine receives a connection and then successful >> login. >> The remote ssh server shows a successful connection and login, and >> windows Task Manager shows a Julia process has started. >> Then the following error occurs on the local machine, after which the >> remote session is terminated. >> >> Error evaluating c:\Users\Greg\Julia6\src\Launcher.jl: >> connect: connection timed out (ETIMEDOUT) >> in wait at task.jl:284 >> in wait at task.jl:194 >> in stream_wait at stream.jl:263 >> in wait_connected at stream.jl:301 >> in Worker at multi.jl:113 >> in create_worker at multi.jl:1064 >> in start_cluster_workers at multi.jl:1028 >> >> I guess my first question is which side (local or remote) is failing. >> It seems to me that the local Julia process is waiting for some >> confirmation of connection? Does that sound right? >> If so, are there any suggestions on how to further diagnose problem. >> >> When the ssh command to start a remote Julia worker is executed from the >> windows command line, I get the following: >> julia_worker:9009#192.168.1.107 >> >> Then after about 60s: >> Master process (id 1) could not connect within 60.0 seconds. >> exiting. >> >> Presumably this is the expected behaviour, since the remote worker >> process is not communicating with master Julia process? >> >> Maybe the remote Julia.exe command is not receiving the --worker argument >> properly? >> >> As I said, my method works in another environment (which incidentally >> seems like magic to me). >> I'm not really sure what is different here. >> So any suggestions would be appreciated. >> >> Thanks, Greg >> > >
Re: [julia-users] Adding remote workers on windows
Is port 9009 open on the remote machine? You could try with "tunnel=true" if it is not open. On Mon, Sep 7, 2015 at 4:32 PM, Greg Plowman wrote: > Hi, > > I'm trying to use addprocs() to add remote workers on another windows > machine. > > I'm using a ssh server for windows (Bitvise) with a modified Cluster > Manager, and have successfully used this method in another environment. > So I know that it works, although one difference is Window 7 (works) vs > Windows 8.1 (does not work), but I don't think this should be problem. > > Now, I don't expect anyone to troubleshoot my particular setup / > environment / customisation. > Rather I was hoping for some high level help with further diagnosis. > > I can confirm that the windows command to launch the remote worker is > executed, and the remote machine receives a connection and then successful > login. > The remote ssh server shows a successful connection and login, and windows > Task Manager shows a Julia process has started. > Then the following error occurs on the local machine, after which the > remote session is terminated. > > Error evaluating c:\Users\Greg\Julia6\src\Launcher.jl: > connect: connection timed out (ETIMEDOUT) > in wait at task.jl:284 > in wait at task.jl:194 > in stream_wait at stream.jl:263 > in wait_connected at stream.jl:301 > in Worker at multi.jl:113 > in create_worker at multi.jl:1064 > in start_cluster_workers at multi.jl:1028 > > I guess my first question is which side (local or remote) is failing. > It seems to me that the local Julia process is waiting for some > confirmation of connection? Does that sound right? > If so, are there any suggestions on how to further diagnose problem. > > When the ssh command to start a remote Julia worker is executed from the > windows command line, I get the following: > julia_worker:9009#192.168.1.107 > > Then after about 60s: > Master process (id 1) could not connect within 60.0 seconds. > exiting. > > Presumably this is the expected behaviour, since the remote worker process > is not communicating with master Julia process? > > Maybe the remote Julia.exe command is not receiving the --worker argument > properly? > > As I said, my method works in another environment (which incidentally > seems like magic to me). > I'm not really sure what is different here. > So any suggestions would be appreciated. > > Thanks, Greg >
