Ubuntu
apport package

  1. Bug #1891657
  2. Comment #44

Comment 44 for bug 1891657

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

On Tue, Sep 29, 2020 at 12:38:38PM -0000, Nicolas Bock wrote:
> Still failing for me. I see now:
>
> Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled...
> Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Succeeded.
> Sep 29 06:32:27 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled.
> Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly.
> Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
> Sep 29 06:32:27 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
> Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.path: Failed with result 'unit-start-limit-hit'.
>
> I have 2 crash files in /var/crash. Note that those two files were in
> /var/crash already on boot, I didn't add anything to this directory.

Could you please run 'systemctl status whoopsie' and include the output
of the command here?

--
Brian Murray