Bugzilla – Bug 4765
Status for vsmagent/vsmserver is "stopped" on systemd systems, even when services are actually running
Last modified: 2013-10-24 11:03:27
You need to
before you can comment on or make changes to this bug.
See issue 14443. Tested on F17 using 4.1.0post (build 4031).
This is because ctccommon expects SysV-style output from a call to
/etc/init.d/<service>, and what it's getting is systemd-style output.
The problem is caused by the service wrapper (that's a fairly new thing).
Instead of looking at the return code, it tries to parse the output.
That wrapper is also a rather pointless abstraction on top of subprocess. So I
think I'll clean things up in the process.
Fixed in r27774 to r27776.
I found that services wouldn't start from tl-setup. The code was trying to call
the init script with the init script name as the first argument. Bugfixed in
*** Bug 4818 has been marked as a duplicate of this bug. ***
We're getting a traceback in tlwebadm (see bug 4818).
(In reply to comment #6)
> We're getting a traceback in tlwebadm (see bug 4818).
Fixed in r27991.
Verified on Fedora 19, ThinLinc build 4118 which includes the new service
wrapper script. Service status is shown correctly from both console and web
There were also no problems to start the service while installing.