apport-autoreport.service fails to start in groovy after upgrading from focal

Bug #1894369 reported by Primož Ajdišek
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Confirmed
Undecided
Brian Murray
Groovy
Confirmed
Undecided
Brian Murray

Bug Description

apport-autoreport.service fails to start with that CPU load increases significantly making computer unusable. disabling the service and path and stopping both normalizes CPU load as it was supposed to be. for test purposes i started apport-autoreport.service and after checking its status i get state: degraded and 2 units failed.

Tags: fr-690 groovy
tags: added: rls-gg-incoming
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin (martid0311) wrote :

I have this issue too. It causes systemd's PID 1 (`/sbin/init splash` in htop) to use 100% CPU, which seems unfortunate.

When it happens, the log is filled with a whole lot of lines like this:

Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

Followed by logs like this:

Sep 11 10:00:02 ubun systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 11 10:00:02 ubun whoopsie-upload-all[25552]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping
Sep 11 10:00:02 ubun whoopsie-upload-all[25552]: All reports processed
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Succeeded.
Sep 11 10:00:02 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled.
Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 11 10:00:02 ubun whoopsie-upload-all[25605]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping
Sep 11 10:00:02 ubun whoopsie-upload-all[25605]: All reports processed
Sep 11 10:00:02 ubun systemd[1]: apport-autoreport.service: Succeeded.
Sep 11 10:00:02 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled.
Sep 11 10:00:02 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 11 10:00:03 ubun whoopsie-upload-all[25622]: /var/crash/_usr_bin_stacer.0.crash already marked for upload, skipping
Sep 11 10:00:03 ubun whoopsie-upload-all[25622]: All reports processed
Sep 11 10:00:03 ubun systemd[1]: apport-autoreport.service: Succeeded.
Sep 11 10:00:03 ubun systemd[1]: Finished Process error reports when automatic reporting is enabled.
Sep 11 10:00:03 ubun systemd[1]: Starting Process error reports when automatic reporting is enabled...

Revision history for this message
Brian Murray (brian-murray) wrote :

Which release of Ubuntu are you running?

Changed in apport (Ubuntu):
assignee: nobody → Brian Murray (brian-murray)
tags: added: groovy
tags: removed: rls-gg-incoming
tags: added: fr-690
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.