Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1367729 - systemctl reload acts on the wrong instance
Summary: systemctl reload acts on the wrong instance
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-17 10:28 UTC by Anand Buddhdev
Modified: 2016-08-18 07:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-08-18 07:17:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Anand Buddhdev 2016-08-17 10:28:57 UTC
Description of problem:

When more than one instance of a system unit exist, systemctl reload does not reload all of them, but only the one started last.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create a systemd unit, and a systemd template with an ExecReload option
2. start the main unit and then start one instance from the template
3. try to reload both of them with "systemctl reload myservice\*"

Actual results:

systemd will reload just one services, but twice.

Expected results:

systemd should reload each service once.

Additional info:


# ll /usr/lib/systemd/system/knot*
-r--r--r-- 1 root root 179 Aug 17 10:07 /usr/lib/systemd/system/knot.service
-r--r--r-- 1 root root 217 Aug 17 10:07 /usr/lib/systemd/system/knot@.service

# diff /usr/lib/systemd/system/knot*
< Description=Knot DNS server daemon
> Description=Knot DNS server %i
< ExecStart=/usr/sbin/knotd
< ExecReload=/usr/sbin/knotc reload
> ExecStart=/usr/sbin/knotd -c /etc/knot/%i.conf
> ExecReload=/usr/sbin/knotc -c /etc/knot/%i.conf reload

Comment 1 Anand Buddhdev 2016-08-18 07:07:52 UTC
Hello. I would like to apologise for this report. There isn't a bug. My unit configuration was incorrect, and both were binding to the same control socket, so the reload command was acting on the wrong daemon.

Note You need to log in before you can comment on or make changes to this bug.