How do I Systemd Disable Userspace Service no Longer Needed?

[Stephen Morris]

Hi,

Looking at failed messages in journalctl I noticed the following messages:


Nov 13 06:47:12 localhost.localdomain systemd[2393]: 
openrazer-daemon.service: Failed to execute command: No such file or 
directory
Nov 13 06:47:12 localhost.localdomain systemd[2393]: 
openrazer-daemon.service: Failed at step EXEC spawning 
/usr/bin/openrazer-daemon: No such file or directory
Nov 13 06:47:12 localhost.localdomain systemd[2386]: 
openrazer-daemon.service: Failed with result 'exit-code'.
Nov 13 06:47:12 localhost.localdomain systemd[2386]: Failed to start 
Daemon to manage razer devices in userspace.

That service was from a vendor supplied package for the mouse I used 
previously.

I tried to disable the service but that failed.


sudo systemctl disable openrazer-daemon.service
Failed to disable unit: Unit file openrazer-daemon.service does not exist.

sudo systemctl disable openrazer-daemon.service --user
Failed to connect to bus: No such file or directory


Given the above how do I stop systemd from trying to start the unneeded 
service?


regards,

Steve

[Rick Stevens]

On 11/12/18 1:37 PM, Stephen Morris wrote:
>  Hi,
>  
>  Looking at failed messages in journalctl I noticed the following messages:
>  
>  
>  Nov 13 06:47:12 localhost.localdomain systemd[2393]:
>  openrazer-daemon.service: Failed to execute command: No such file or
>  directory
>  Nov 13 06:47:12 localhost.localdomain systemd[2393]:
>  openrazer-daemon.service: Failed at step EXEC spawning
>  /usr/bin/openrazer-daemon: No such file or directory
>  Nov 13 06:47:12 localhost.localdomain systemd[2386]:
>  openrazer-daemon.service: Failed with result 'exit-code'.
>  Nov 13 06:47:12 localhost.localdomain systemd[2386]: Failed to start
>  Daemon to manage razer devices in userspace.
>  
>  That service was from a vendor supplied package for the mouse I used
>  previously.
>  
>  I tried to disable the service but that failed.
>  
>  
>  sudo systemctl disable openrazer-daemon.service
>  Failed to disable unit: Unit file openrazer-daemon.service does not exist.
>  
>  sudo systemctl disable openrazer-daemon.service --user
>  Failed to connect to bus: No such file or directory
>  
>  
>  Given the above how do I stop systemd from trying to start the unneeded
>  service?
>  
First, find the actual name of the service file (it's probably NOT
"openrazer-daemon.service" as the service file itself often isn't named
after the daemon it runs). You could try:

	find /usr/lib/systemd -name "*razer*"

and if that fails to find anything:

	find /etc/systemd -name "*razer*"

Once you find it, then:

	systemctl disable <name-of-service-file>

if you MAY use it again (via "enable" or "link"), or

	systemctl mask <name-of-service-file>

if you don't plan to ever use it again.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-    Overweight:  When you step on your dog's tail...and it dies.    -
----------------------------------------------------------------------

[Samuel Sieb]

On 11/12/18 1:59 PM, Rick Stevens wrote:
>  On 11/12/18 1:37 PM, Stephen Morris wrote:
> > Looking at failed messages in journalctl I noticed the following messages:
> >
> > Nov 13 06:47:12 localhost.localdomain systemd[2393]:
> > openrazer-daemon.service: Failed to execute command: No such file or
> > directory
>  First, find the actual name of the service file (it's probably NOT
>  "openrazer-daemon.service" as the service file itself often isn't named
>  after the daemon it runs). You could try: 
The log says "openrazer-daemon.service", so that is what you pass to 
systemctl, although you can drop the ".service" part.

[Joe Zeff]

On 11/12/2018 02:37 PM, Stephen Morris wrote:
>  
>  Given the above how do I stop systemd from trying to start the unneeded 
>  service? 
Try this:

systemctl list-unit-files | grep openr

This will work as long as the service's name has openr somewhere.

[Tom Horsley]

>  Given the above how do I stop systemd from trying to start the
> unneeded 
>  service? 
I went on a long drawn out quest to find this and wrote
it up here:

https://tomhorsley.com/game/punch.html#User%20Daemons

[Samuel Sieb]

On 11/12/18 1:37 PM, Stephen Morris wrote:
>  sudo systemctl disable openrazer-daemon.service --user
>  Failed to connect to bus: No such file or directory 
It's a user service, so don't use "sudo".

>  Given the above how do I stop systemd from trying to start the
> unneeded 
>  service? 
The previous command should work without the sudo.

[Resolved]: How do I Systemd Disable Userspace Service no Longer Needed?

[Stephen Morris]

On 13/11/18 3:43 pm, Samuel Sieb wrote:
>  On 11/12/18 1:37 PM, Stephen Morris wrote:
> > sudo systemctl disable openrazer-daemon.service --user
> > Failed to connect to bus: No such file or directory
>
>  It's a user service, so don't use "sudo".
>
> > Given the above how do I stop systemd from trying to start the 
> > unneeded service?
>
>  The previous command should work without the sudo. 
Thankyou to everyone who helped with this, issuing the systemctl user 
space command without sudo did remove the service. This also highlights 
that when I was looking manually for the service file I overlooked 
/usr/lib/systemd/user.


regards,

Steve


> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]