# Ignition running on SuSE Leap + systemd service

**URL:** <https://forum.inductiveautomation.com/t/ignition-running-on-suse-leap-systemd-service/63114>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [August 17, 2022, 7:29pm UTC](https://forum.inductiveautomation.com/t/ignition-running-on-suse-leap-systemd-service/63114 "2022-08-17T19:29:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fred\_Morris](https://avatars.discourse-cdn.com/v4/letter/f/ce73a5/32.png) [@Fred\_Morris](https://forum.inductiveautomation.com/u/Fred_Morris)\
**Post date:** [August 17, 2022, 7:29pm UTC](https://forum.inductiveautomation.com/t/ignition-running-on-suse-leap-systemd-service/63114/1 "2022-08-17T19:29:11Z")

</div>

Hello, although I suspect it’s not the intended _Linux_ target, _Ignition_ runs just fine on _SuSE Leap 15.3_ in a virtual machine (KVM/qemu).

- Headless install (command line) was fine after creating the user and group `ignition:ignition`.
- `fontconfig` was already installed.
- Needed to install `sysvinit-tools` to obtain `pidof` (required to successfully launch the application after installation).

Connectivity from the host operating system was initially blocked by _firewalld_, which I disabled (along with _AppArmor_). This manifested as the VM returning an ICMP host unreachable.

No _systemd_ service file was installed so I created one. If you examine the contents you will see that it has a second commented out mode besides `forking`. In the other mode it runs in the console, and you can monitor the logging with e.g. `journalctl -uignition -f`. I don’t know which one is best, it would be nice if there was an official service file.

I’m apparently unable to attach the service file, so here it is:

```auto
[Unit]
Description=Ignition SCADA
After=network.target

# cat ignition.service
[Service]
User=ignition
Group=ignition
Type=forking
ExecStart=/usr/local/bin/ignition/ignition.sh start
ExecStop=/usr/local/bin/ignition/ignition.sh stop
# There is also a console mode
#Type=simple
#ExecStart=/usr/local/bin/ignition/ignition.sh console

[Install]
WantedBy=multi-user.target

```

---

<div class="post-metadata">

**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:** [August 17, 2022, 7:37pm UTC](https://forum.inductiveautomation.com/t/ignition-running-on-suse-leap-systemd-service/63114/2 "2022-08-17T19:37:34Z")

</div>

The closest thing to an “official” one would be whatever the Java Service Wrapper shell script generates when it detects systemd as the service mechanism.

Look at the `systemdInstall()` function in `ignition.sh` and copy what it appears to output.

(it uses forking)