RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

systemctl start/stop/restart service doesn't display success.  it would be nice to get something like an "OK service has started, or OK service has stopped ... etc.

this would be more inline with our chkconfig or service based commands from rhel 5/6.


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

rhel 7


How reproducible:

run systemctl stop/start/restart any service


Expected results:

Information should be display after the command is run to show that it was successful or failed.


Additional info:

Customers new to systemctl may question if the command has run - the only way to confirm that the service is now running or now stopped is to run the systemctl status command.

Is this really a problem? It common practice in linux world that tools are silent on success and prints error messages on failure.

I guess I'm just used to seeing the Ok/FAILURE from the RHLE4/5/6 service commands that it would be nice to see with systemctl.  I know some of my customers have made the same comments.

We have already discussed that. Maybe in the future we could add some verbose option to systemctl, but I don't think that this could help in all cases. For example when you have service with Type=simple systemctl will just tell pid1 to start it and returns without waiting to anything.

*** This bug has been marked as a duplicate of bug 978955 ***