# Ansible Tower can't reach SCM source or remote host.

**URL:** <https://forum.ansible.com/t/ansible-tower-cant-reach-scm-source-or-remote-host/26689>\
**Category:** Ansible Project\
**Tags:** windows, ubuntu\
**Created:** [February 8, 2018, 8:16pm UTC](https://forum.ansible.com/t/ansible-tower-cant-reach-scm-source-or-remote-host/26689 "2018-02-08T20:16:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pranav\_Baitule](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pranav\_Baitule](https://forum.ansible.com/u/Pranav_Baitule)\
**Post date:** [February 8, 2018, 8:16pm UTC](https://forum.ansible.com/t/ansible-tower-cant-reach-scm-source-or-remote-host/26689/1 "2018-02-08T20:16:02Z")

</div>

Hello,

I have installed Ansible Tower on Ubuntu using Windows Subsystem for Linux.

Starting an SCM update or running a playbook against a remote host gives me the following error -

`

Can’t create signalfd: Function not implemented

Failed to make / slave: Invalid argument

`

How can I fix this?

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [February 9, 2018, 11:37am UTC](https://forum.ansible.com/t/ansible-tower-cant-reach-scm-source-or-remote-host/26689/2 "2018-02-09T11:37:52Z")

</div>

WSL doesn’t support every function available in the linux kernel unfortunately.

There’s a bug report open for signalfd here

[https://github.com/Microsoft/WSL/issues/129](https://github.com/Microsoft/WSL/issues/129)

If I recall Tower wants a fair bit of RAM etc so you are probably better off spinning up a dedicated VM for it.

Hope this helps,

Jon

---

<div class="post-metadata">

**Author:** ![Pranav\_Baitule](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pranav\_Baitule](https://forum.ansible.com/u/Pranav_Baitule)\
**Post date:** [February 9, 2018, 7:49pm UTC](https://forum.ansible.com/t/ansible-tower-cant-reach-scm-source-or-remote-host/26689/3 "2018-02-09T19:49:43Z")

</div>

Ah. Everything works now with a dedicated VM. Thank you.
