Bug 1069306

I was able to reproduce my problem also on RHEL7 with systemd-208-4.el7

following is the comment which explains the root cause:


+++ This bug was initially created as a clone of Bug #1068542 +++

--- Additional comment from Michal Schmidt on 2014-02-24 10:04:28 EST ---

systemd-journald is a bit special in the way its socket survives the switch-root from the initramfs. Nevertheless, here's a reproducer that involves neigher initramfs nor systemd-journald:

1. Make sure a socket and its service are both "active (running)":
     systemctl start avahi-daemon.{socket,service}
2. Mask only the service:
     systemctl mask avahi-daemon.service
3. Stop the service:
     systemctl stop avahi-daemon.service
4. Check the resulting statuses:
     systemctl status avahi-daemon.{socket,service}

Actual result: Though the service is now inactive, the socket unit is still "active (running)". This is an inconsistency.
Expected result: The socket should be at most "active (listening)", so it can go into "failed" by itself when a connection is attempted.

I think the socket failed to notice the death of the service because socket_trigger_notify() returns early if the service's load state is UNIT_MASKED (!= UNIT_LOADED).