# Starting the controller using systemd on an Oracle Linux machine

**URL:** <https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811>\
**Category:** Ziti Overlay\
**Created:** [October 14, 2022, 4:46am UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811 "2022-10-14T04:46:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![markamind](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/markamind/32/157_2.png) [@markamind](https://openziti.discourse.group/u/markamind)\
**Post date:** [October 14, 2022, 4:46am UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811/1 "2022-10-14T04:46:28Z")

</div>

When you start the controller with systemd on an Oracle Linux machine… it fails to start due to a conflict with SELinux.

One thing I have not tried yet is to install OpenZiti in another folder like /etc/ instead of /home/opc/

Would this resolve the issue?

It’s come to the point to where I now need to find an answer.

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [October 16, 2022, 12:07pm UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811/2 "2022-10-16T12:07:23Z")

</div>

This helpful at all? Was just published

> **[Setting Up Oracle Cloud To Host OpenZiti](https://openziti.io/setting-up-oracle-cloud-to-host-openziti)**
>
> For a long time, I've been concerned about relying on a company's focus on security. I generally expect the least focus on security as many companies just want to be first to market. Yikes, that sounds bad, but many companies indeed focus too little...

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [October 16, 2022, 12:08pm UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811/3 "2022-10-16T12:08:07Z")

</div>

Oh nevermind, I see he used Ubuntu. Probably not relevant to Oracle Linux

---

<div class="post-metadata">

**Author:** ![markamind](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/markamind/32/157_2.png) [@markamind](https://openziti.discourse.group/u/markamind)\
**Post date:** [October 16, 2022, 12:15pm UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811/4 "2022-10-16T12:15:46Z")

</div>

I am going to try to install Ziti in the etc folder to see if this resolve the issue… as it seems to be a folder rights issue… as a guess

---

<div class="post-metadata">

**Author:** ![av-dev](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@av-dev](https://openziti.discourse.group/u/av-dev)\
**Post date:** [October 17, 2022, 6:42pm UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811/5 "2022-10-17T18:42:47Z")

</div>

IIRC I ran into similar issue, if you run `sudo systemctl enable <systemd-unit>` it will make a symlink in `/etc/systemd/system` and that should help with SELinux restrictions.

---

<div class="post-metadata">

**Author:** ![markamind](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/markamind/32/157_2.png) [@markamind](https://openziti.discourse.group/u/markamind)\
**Post date:** [October 17, 2022, 9:45pm UTC](https://openziti.discourse.group/t/starting-the-controller-using-systemd-on-an-oracle-linux-machine/811/6 "2022-10-17T21:45:51Z")

</div>

Super helpful. Thanks so much for sharing… its certainly saved a lot of painful trial and error.