# \[Bug-16797\] Ignition Gateway Start on Linux on boot **URL:** \ **Category:** Ignition\ **Created:** [June 22, 2019, 1:08pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033 "2019-06-22T13:08:14Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![bridress1](https://avatars.discourse-cdn.com/v4/letter/b/bbce88/32.png) [@bridress1](https://forum.inductiveautomation.com/u/bridress1)\ **Post date:** [June 22, 2019, 1:08pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/1 "2019-06-22T13:08:14Z")
We are running Ignition 7.9.10 as an OPC server on a Linux headless host (Ubuntu). We have another Ignition instance that is running our project/tag configurations which connects to the OPC server. We have lost power to the host a few times and it seemed Ignition failed to start back up cleanly. I needed to Putty on and start the Ignition gateway. Do we need to configure Linux to startup Ignition Gateway on boot up or is this already handled during the initial install? If so I assume I need to give the start script root creds and run the following script (“sudo some directory ./ignition.sh start”) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [June 22, 2019, 1:51pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/2 "2019-06-22T13:51:55Z")
You should be able to run `./ignition.sh install` to install it as a service. ---
**Author:** ![bridress1](https://avatars.discourse-cdn.com/v4/letter/b/bbce88/32.png) [@bridress1](https://forum.inductiveautomation.com/u/bridress1)\ **Post date:** [June 23, 2019, 5:31am UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/3 "2019-06-23T05:31:44Z")
Thanks Kevin. Is there a way I can check first that it is running as a service? I’ll probably try a clean restart today of the host to see if it starts up. ---
**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\ **Post date:** [June 24, 2019, 9:43am UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/4 "2019-06-24T09:43:52Z")
This depends on your version of Ubuntu, but for most recent versions, you can use the `systemctl` command (as root). These are pretty simple commands: `systemctl status ignition` – Check the status `systemctl start ignition` – Start it now `systemctl stop ignition` – Stop it now `systemctl enable ignition` – Autostart on boot `systemctl disable ignition` – Remove the autostart symlinks Older versions of Ubuntu generally use init scripts. ---
**Author:** ![Santhoshkumar.G](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@Santhoshkumar.G](https://forum.inductiveautomation.com/u/Santhoshkumar.G)\ **Post date:** [July 15, 2020, 9:18am UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/5 "2020-07-15T09:18:24Z")
> [@Sanderd17](#): > > `systemctl status ignition` – Check the status > `systemctl start ignition` – Start it now > `systemctl stop ignition` – Stop it now > `systemctl enable ignition` – Autostart on boot > `systemctl disable ignition` – Remove the autostart symlinks Hi, Can you confirm, how can I do same with RHEL version 8. Am not able to use above commands in RHEL v8., getting error " Unit not found". But service is running. ---
**Author:** ![Santhoshkumar.G](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@Santhoshkumar.G](https://forum.inductiveautomation.com/u/Santhoshkumar.G)\ **Post date:** [July 15, 2020, 9:19am UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/6 "2020-07-15T09:19:24Z")
OS version RHEL 8 Ignition Gateway version 8.0.14 ---
**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\ **Post date:** [July 15, 2020, 9:36am UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/7 "2020-07-15T09:36:37Z")
Can you show the contents of the `ignition.service` file (usually in `/etc/systemd/system` or `/lib/systemd/system`)? `Unit` is a part of that file, so systemd not finding it sounds like your service file is corrupt in some way. Perhaps reinstalling works too? ---
**Author:** ![Santhoshkumar.G](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@Santhoshkumar.G](https://forum.inductiveautomation.com/u/Santhoshkumar.G)\ **Post date:** [July 15, 2020, 12:37pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/8 "2020-07-15T12:37:13Z")
Below are the content from service file, [Unit] Description=Ignition-Gateway After=syslog.target [Service] Type=forking ExecStart=/usr/local/bin/ignition/ignition.sh start sysd ExecStop=/usr/local/bin/ignition/ignition.sh stop sysd User=root KillMode=control-group Environment=SYSTEMD\_KILLMODE\_WARNING=true [Install] WantedBy=multi-user.target ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 15, 2020, 1:44pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/9 "2020-07-15T13:44:29Z")
In current versions of Ignition, I believe the unit file has been renamed to “Ignition Gateway.service” or something like that. I’m still using “ignition.service” for my custom Zip installs. Unit files really should not have a space, and I don’t know of any with uppercase letters… ---
**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\ **Post date:** [July 15, 2020, 2:58pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/10 "2020-07-15T14:58:19Z")
So now you need to `systemctl start "Ignition Gateway"` ? That’s annoying. Thanks for the correction in any case. I didn’t have a recent systemd with Ignition install handy. Most of our test projects run in a docker (which uses Alpine and thus openRC). ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 15, 2020, 3:47pm UTC](https://forum.inductiveautomation.com/t/bug-16797-ignition-gateway-start-on-linux-on-boot/26033/11 "2020-07-15T15:47:26Z")
Hmm, I agree that the unit being renamed is probably wrong. I’ll see if that was intentional or not.