-
Notifications
You must be signed in to change notification settings - Fork 138
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
USBGuard daemon won't start at booting. #591
Comments
Could you elaborate what you mean by "service in Systemd don't start at boot", e.g. what you did to make that happen, is the service enabled, any related error logs etc? Thanks! |
I've installed usbguard with "sudo apt install usbguard" and added the line "allow id 045e:0745" in /etc/usbguard/rules.conf and since the service blocks every device that isn't registered in rules.conf it works fine but if i leave a pendrive connected when i'm booting the system i will be able to use it until i manually restart the usbguard.service. The following is the result to "systemctl status usbguard.service": mai 26 10:54:36 ESTRES-0524 systemd[1]: Failed to start USBGuard daemon. |
There are some things that are not clear to me yet in your scenario, would be great to fully understand. |
Apparently, the service works when I turn on the machine, but it stops working and starts giving an error in the daemon until it stops with the message: Failed with result 'start-limit-hit'. Therefore, if I turn on the machine with a connected USB drive (in this case, the USB drive should be blocked), I can use it normally. When I checked the status of the usbguard.service, I noticed the following logs: usbguard.service: Start request repeated too quickly. I can only block the use of the USB by restarting the service with the command "sudo systemctl restart usbguard.service." |
I believe this line is the first clue to what's going on: Apparantly something in your system is killing/stopping usbguard from the outside. If you compair this to running |
Thank you for helping, I will identify what is causing this and come back here if I still need assistance. |
@vinismm please come back with an update in any case, so that we can learn from your case and close the ticket as needed. Thank you! |
@hartwork I had the same issue on Arch after migrating my PC setup to my laptop:
If I start the it manually as you described:
The following is the output:
After issuing I think as a potential improvement usbguard could output the aforementioned |
Hi everyone, the issue is not currently in an actionable state: file permissions are either a usage or a packaging problem, likely not a bug in the actual software. Changes to logging would need a closer look. I'm happy to jump on a voice call with someone if you're convince that there is a bug to fix here, and turn that call into a pull request, to then hopefully be merged by RedHat after, I lack permissions. That's the only thing I can offer time for right now, my e-mail contact is on my GitHub profile. |
I couldn't agree more, you might have misunderstood (or did not read the whole comment of mine?) I just think that the error is not represented in the log of the systemd service, so as a potential improvement, error logs should be somehow made sure that they are actually logged by the daemon into the systemd service. This would allow users to correct the underlying configuration issue or help them make an accurate report to downstream, if the issue is cause by for instance incorrect packaging. |
Hello,
I've installed usbguard on Mint 20.3 everything works fine, but the service in Systemd don't start at boot...
If I start the machine with a blocked device connected the service won't block it and i have to restart the usbguard.service for it to work as intended.
Does anyone have a solution for that problem?
The text was updated successfully, but these errors were encountered: