Public bug reported:
The systemd service generated from /etc/init.d/apache2 via systemd-sysv-
generator contains the line
RemainAfterExit=yes
causing systemd to ignore crashes of the service. In order to reproduce
this, add a non-existing address to /etc/apache2/ports.conf, which will
cause the apache2 service to fail.
However, "systemctl status apache2" will still show "active(exited)",
e.g. will not recognize the service as failed. In particular, "systemctl
is-failed apache2" will still return "active" instead of "failed".
Expected result: "systemctl is-failed apache2" should return "failed",
so that monitoring script can detect the error.
The solution would probably be to include a proper native systemd
service definition instead of using the converted sysv service.
$ apt-cache policy apache2
apache2:
Installed: 2.4.10-9ubuntu1.1
Candidate: 2.4.10-9ubuntu1.1
Version table:
*** 2.4.10-9ubuntu1.1 0
500 http://eu.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64
Packages
100 /var/lib/dpkg/status
2.4.10-9ubuntu1 0
500 http://eu.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488962
Title:
systemd does not notice when apache2 service fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
