Your message dated Tue, 16 Nov 2021 22:05:55 +0000 with message-id <[email protected]> and subject line Re: [usbguard] service start issues - start request repeated too quickly?? has caused the Debian Bug report #970561, regarding [usbguard] service start issues - start request repeated too quickly?? to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 970561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970561 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: usbguard Version: 0.7.8+ds-2 I'm experiencing some failures getting the service started cleanly. I'll briefly explain how I got to this, if I can recall correctly. I just had a need to use my printer (unused for quite some time), which I connected via USB. Nothing was happening when I tried to print, so I suspected usbguard, and indeed the printer was being blocked as unauthorised per dmesg output. Not wanting to have to try to craft my own rule for the printer, I deleted the rules.conf, had aptitude reinstall usbguard to auto-generate a new one with the printer included (double checking the details, confirming that it just added an entry). I believe at this point I re-added the following custom rules to the end and got the service restarted, before successfully printing, or maybe I printed first: ``` allow with-interface equals { 08:*:* } reject with-interface all-of { 08:*:* 03:00:* } reject with-interface all-of { 08:*:* 03:01:* } reject with-interface all-of { 08:*:* e0:*:* } reject with-interface all-of { 08:*:* 02:*:* } ``` I then plugged in a USB pendrive (which usbguard has never blocked before), but could not access it, and dmesg was indicating usbguard blocking it, strangely. Restarting the service did not help, so I had to reboot, at which point it then worked. (Does the service have an issue re-reading the rules on restarting?). (Edit: To be clear with the above, I'm pretty certain that I stopped the service first, then started it again, and repeatedly asked it to start until it did so successfully, per status output, and it would not let me use the pendrive until after rebooting). Getting to the point, when trying to restart the service, I also checked the status afterwards to double check, only to find the following: ``` $ sudo systemctl start usbguard $ sudo systemctl status usbguard ● usbguard.service - USBGuard daemon Loaded: loaded (/lib/systemd/system/usbguard.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-09-18 17:12:58 BST; 15s ago Docs: man:usbguard-daemon(8) Process: 2673 ExecStart=/usr/sbin/usbguard-daemon -k -c /etc/usbguard/usbguard-daemon.conf (code=exited, status=1/FAILURE) Main PID: 2673 (code=exited, status=1/FAILURE) Sep 18 17:12:58 debian1 systemd[1]: usbguard.service: Scheduled restart job, restart counter is at 5. Sep 18 17:12:58 debian1 systemd[1]: Stopped USBGuard daemon. Sep 18 17:12:58 debian1 systemd[1]: usbguard.service: Start request repeated too quickly. Sep 18 17:12:58 debian1 systemd[1]: usbguard.service: Failed with result 'exit-code'. Sep 18 17:12:58 debian1 systemd[1]: Failed to start USBGuard daemon. Sep 18 17:13:00 debian1 systemd[1]: usbguard.service: Start request repeated too quickly. Sep 18 17:13:00 debian1 systemd[1]: usbguard.service: Failed with result 'exit-code'. Sep 18 17:13:00 debian1 systemd[1]: Failed to start USBGuard daemon. ``` It would take multiple attempts at asking it to start for it to report started successfully. Now, upon that reboot, I noticed red error indicators in the console output (they may well have been there before without my noticing), against services usbguard and usbguard-dbus. So the first thing I did upon logging in was to double-check the status, and finding them failed, tried to restart them. I asked first usbguard to start, then usbguard-dbus, with the latter reporting failure due to "a dependency job" failing. I checked the usbguard status, finding it still down due to some failure. I asked it to start again, checked the status, and it was then up. I then again asked usbguard-dbus to start, which did not result in a dependency error this time. But then I immediately checked the usbguard (not usbguard-dbus) status, and found it down again for some reason, yet then checking usbguard-dbus status, that was up. I double checked usbguard, and indeed it was still down, while usbguard-dbus was up. So I asked usbguard to start once more, and again it then reported being up. I've just double checked the status after writing this, and usbguard is down again with error for some reason, while usbguard-dbus remains up.
--- End Message ---
--- Begin Message ---control: fixed 1.0.0+ds-1 Update: Since reporting this bug I've been putting up with a slew of failure entries from usbguard within the console output during boot, hoping that some day the bug I'd reported would be fixed and these failures would go away. The other day however I happened to discover that at some point I'd managed to corrupt my config file via a bad copy & paste job. Having fixed that, I no longer get any usbguard failures during boot up, and if I try to stop and start the `usbguard` and `usbguard-dbus` services this now happens perfectly cleanly unlike what I was experiencing before. So I guess the bug was actually fixed in 1.0.0+ds-1.
--- End Message ---
