# ERROR: option '--worker' is missing an argument

**URL:** <https://discourse.julialang.org/t/error-option-worker-is-missing-an-argument/1355>\
**Category:** General Usage\
**Created:** [January 8, 2017, 5:56pm UTC](https://discourse.julialang.org/t/error-option-worker-is-missing-an-argument/1355 "2017-01-08T17:56:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![noel\_ryan](https://avatars.discourse-cdn.com/v4/letter/n/e19adc/32.png) [@noel\_ryan](https://discourse.julialang.org/u/noel_ryan)\
**Post date:** [January 8, 2017, 5:56pm UTC](https://discourse.julialang.org/t/error-option-worker-is-missing-an-argument/1355/1 "2017-01-08T17:56:41Z")

</div>

Hi folks,  
I am trying to connect a windows julia session to a linux session using the following:  
addprocs([“user@host”], dir=“full path directory structure”, exename=“path to julia executable”)  
I am getting the error message

ERROR: option ‘–worker’ is missing an argument

Does anybody know what is causing this or what argument I am missing. Or if anybody has connected windows to linux please do you have any advice.

Thanks in advance,

Noel

---

<div class="post-metadata">

**Author:** ![jameson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jameson/32/23_2.png) [@jameson](https://discourse.julialang.org/u/jameson)\
**Post date:** [January 9, 2017, 10:05pm UTC](https://discourse.julialang.org/t/error-option-worker-is-missing-an-argument/1355/2 "2017-01-09T22:05:37Z")

</div>

I think Windows workers may not be compatible with other workers.

---

<div class="post-metadata">

**Author:** ![lage](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lage/32/2085_2.png) [@lage](https://discourse.julialang.org/u/lage)\
**Post date:** [September 9, 2018, 2:47pm UTC](https://discourse.julialang.org/t/error-option-worker-is-missing-an-argument/1355/3 "2018-09-09T14:47:40Z")

</div>

hi @noel_ryan,

I’m not sure if this is your situation, but it might be that **Master and Workers run different Julia versions**.

I got the same error when trying to connect Docker containers (Master and Workers) in a Linux environment. Master had Julia 0.6.2 and Workers Julia 0.4.7. When I fixed it by setting up the Workers to use the Julia 0.6.2 binary, it worked.

BTW, try to run the following command at the Windows machine (on which I assume the Master process is running):

```bash
ssh -i $ssh_key -o "StrictHostKeyChecking no" user@linux-machine-address

```

If you managed to login, this is not an SSH issue. In this case, it **might** be that Windows and Linux implementations of transport protocol TCP are not compatible. Master and Workers communicate over TCP. [Read here the docs](https://docs.julialang.org/en/v1/manual/parallel-computing/index.html#ClusterManagers-1).

Best,

André Lage.
