Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The usbguard Daemon won't start at booting #68

Closed
amenophobis opened this issue May 19, 2016 · 7 comments
Closed

The usbguard Daemon won't start at booting #68

amenophobis opened this issue May 19, 2016 · 7 comments
Assignees
Labels
Milestone

Comments

@amenophobis
Copy link

Hello,

I've installed usbguard from the copr repo on fedora 23... everything works fine, but when I enable the service in Systemd it don't start at boot...

everytime I need to start the service manually...

does anyone have a solution for that problem?

@genodeftest
Copy link
Contributor

genodeftest commented May 20, 2016

I don't have this problem. What's the output of $ systemctl status usbguard.service after boot but before starting it manually?

Mine:

● usbguard.service - USBGuard daemon
   Loaded: loaded (/usr/lib/systemd/system/usbguard.service; enabled; vendor preset: 
   Active: inactive (dead)

On the second line it reads "enabled". If yours doesn't, it is not enabled. If it failed to start or stopped, you should see an error message.

@dkopecek
Copy link
Member

@amenophobis Thanks for the report. Could you please share the output of systemctl status as mentioned in the previous comment and also the output of

$ sudo journalctl -u usbguard.service -r

@amenophobis
Copy link
Author

amenophobis commented May 20, 2016

The output:

systemctl status usbguard.service

● usbguard.service - USBGuard daemon
   Loaded: loaded (/usr/lib/systemd/system/usbguard.service; enabled; vendor preset: disabled)
   Active: inactive (dead)

Vendor preset not good?

@dkopecek
The log on my Computer is at the moment not very useful, because I started the service with a cronjob for root at boot... this has worked!!!

I have turned off the cronjob and send you the useful log today...

thanks for help...

@dkopecek
Copy link
Member

@amenophobis I reproduced the issue. The problem seems to be in the Install section of the unit. The WantedBy= value should be basic.target instead of base.target.

@dkopecek
Copy link
Member

@genodeftest Is it working for you with WantedBy=base.target? I wonder what could be the real problem. I don't really remember how I got to the "base.target" value as systemd.special(7) doesn't mention it.

@amenophobis
Copy link
Author

amenophobis commented May 20, 2016

@dkopecek I changed it... works perfect...

@dkopecek dkopecek added the bug label May 20, 2016
@dkopecek dkopecek added this to the v0.5 milestone May 20, 2016
@dkopecek dkopecek self-assigned this May 20, 2016
@genodeftest
Copy link
Contributor

Works fine for me with WantedBy=base.target. Might depend on systemd version, mine is 229-7 on Fedora 24 Beta. Changing it to WantedBy=basic.target seems to be the right way to do though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants