# Failing to start with systemd and unexplained issues

**URL:** <https://discourse.haproxy.org/t/failing-to-start-with-systemd-and-unexplained-issues/849>\
**Category:** Help!\
**Created:** [December 10, 2016, 6:45pm UTC](https://discourse.haproxy.org/t/failing-to-start-with-systemd-and-unexplained-issues/849 "2016-12-10T18:45:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [October 28, 2017, 7:32am UTC](https://discourse.haproxy.org/t/failing-to-start-with-systemd-and-unexplained-issues/849/4 "2017-10-28T07:32:30Z")

</div>

Do not use the init.d file.

You are using systemd, you have use the systemd unit file and wrapper, not the init.d script.

```
rm /etc/init.d/haproxy
cd contrib/systemd
cp haproxy.service.in /lib/systemd/system/
systemctl daemon-reload
systemctl enable haproxy
systemctl start haproxy
systemctl status haproxy

```

Note: Haproxy 1.8 and later needs to be compiled with USE\_SYSTEMD=1 for the provided systemd unit file to work (needs systemd header files, that would be `libsystemd-dev` on Debian/Ubuntu or `systemd-devel` on CentOS 7+ afaik).

---

_[View the full topic](https://discourse.haproxy.org/t/failing-to-start-with-systemd-and-unexplained-issues/849)._