Hmm, the tunnel option is expected to work when only the ssh port is open. Is it possible that the ssh connection setup is throwing up a dialog in the background?
For example, when using a keyfile to login to an AWS instance, I use sshflags = `-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=ERROR -i $(ec2_keyfile)` which prevents the "add to hosts file" dialog from popping up. On Fri, Jul 10, 2015 at 3:49 AM, Avik Sengupta <[email protected]> wrote: > I believe azure VM's by default are firewalled off. Have you opened the > TCP ports that Julia uses to communicate? > > > On Thursday, 9 July 2015 17:33:45 UTC+1, András Kalmár Nagy wrote: >> >> I tried tunnel=true... I can now see julia worker processes being spawned >> on the remote machine, which is a good thing, but after a while, nothing >> happens and they die. On the local side, I get this error: >> >> ERROR: 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 anonymous at task.jl:905 >> >> I'm still trying some things. Does julia use ~/.ssh/config? >> >> On Thursday, July 9, 2015 at 4:30:03 PM UTC+2, Amit Murthy wrote: >>> >>> keyword option "tunnel=true" could help >>> >>> On Thu, Jul 9, 2015 at 7:53 PM, András Kalmár Nagy < >>> [email protected]> wrote: >>> >>>> Hi everyone! >>>> >>>> I configured an Azure instance for passwordless SSH, and I can connect >>>> to it without problems from my shell, but Julia fails to connect and I get >>>> timed out after 60 secs. >>>> >>>> I tried putting the host in a machinefile, using it through addprocs >>>> (all combinations of specifying an explicit username and/or IP instead of >>>> the hostname). >>>> >>>> The julia executable is in the same place on all machines, I can >>>> connect to two other machines on the LAN, and they work. >>>> >>>> What could be the problem? >>>> >>> >>>
