Bug 825871

Summary:	'service dirsrv start' no longer works
Product:	[Fedora] Fedora	Reporter:	Edward Z. Yang <ezyang>
Component:	389-ds	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	nhosoi, nkinder, rmeggins
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-04 22:38:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Edward Z. Yang 2012-05-28 20:29:14 UTC

The 'service' binary is intended to work as a backwards-compatibility wrapper around systemd.  However, 'service start dirsrv' no longer works, because you must start dirsrv using 'systemctl start dirsrv.target', not 'systemctl start dirsrv.service'. The latter fails with "No such file or directory."

Comment 1 Rich Megginson 2012-06-01 19:27:18 UTC

If we were to support service, things like

service start dirsrv inst-name

would not work, nor is there a way to make it work, meaning the service command would work differently on systemd platforms and non-systemd platforms.  Is this acceptable?

Comment 2 Edward Z. Yang 2012-06-02 05:30:35 UTC

I don't mind if you don't support service; but it shouldn't fail silently. ;-)

Comment 3 Edward Z. Yang 2012-06-02 15:33:18 UTC

In particular:

[root@whole-enchilada ~]# service dirsrv stop
Redirecting to /bin/systemctl  stop dirsrv.service
[root@whole-enchilada ~]# echo $?
0
[root@whole-enchilada ~]# systemctl status dirsrv
dirsrv - 389 Directory Server scripts.
	  Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled)
	  Active: active (running) since Thu, 31 May 2012 23:00:33 -0400; 1 day and 12h ago
	 Process: 2947 ExecStopPost=/bin/rm -f /var/run/dirsrv/slapd-%i.pid (code=exited, status=0/SUCCESS)
	 Process: 3292 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid -w /var/run/dirsrv/slapd-%i.startpid (code=exited, status=0/SUCCESS)
	Main PID: 3293 (ns-slapd)
	  CGroup: name=systemd:/system/dirsrv@.service/scripts
		  └ 3293 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-scripts -i /var/run/dirsrv/slapd-scripts.pid -w /var/run/dirsrv/slapd-scrip...

Comment 4 Rich Megginson 2012-07-31 17:58:22 UTC

Upstream ticket:
https://fedorahosted.org/389/ticket/423

Comment 5 Nathan Kinder 2013-03-04 22:38:32 UTC

The silent failing issue was fixed in upstream ticket 457, which went out in 389-ds-base-1.2.11.15-1:

  https://fedorahosted.org/389/ticket/457

That said, the service command is not supported.

Closing this ticket.