Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Tue, Sep 29, 2020 at 4:10 PM Nicolas Bock <1891...@bugs.launchpad.net> wrote: > On Tue, Sep 29 2020, Brian Murray wrote: > > > On Tue, Sep 29, 2020 at 12:38:38PM -, Nicolas Bock wrote: > > Could you please run 'systemctl status whoopsie' and > > include the output of the command here? > > $ sudo systemctl status whoopsie > > I had a few minutes to boot my U-MATE 20.10 distro that is so slow to boot . . . . I checked "ls var/crash" and it showed three files there, when one of the last times I booted it up I trashed the whole directory, as was suggested to try to improve boot times . . . at first it seemed to but today wasn't very good as far as comparing ubuntu to my other options. I then ran the requested "whoopsie" command and got at least ten blocks of lines claiming to be "19 lines" spaced out with blackness between them . . . I copied one of the blocks, looks fairly similar to the previous posting?? [CODE] whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 11:26:52 PDT; 12min ago Main PID: 1902 (whoopsie) Tasks: 3 (limit: 19101) Memory: 7.9M CGroup: /system.slice/whoopsie.service └─1902 /usr/bin/whoopsie -f Sep 30 11:26:52 non1-MacPro systemd[1]: Started crash report submission daemon. Sep 30 11:26:52 non1-MacPro whoopsie[1902]: [11:26:52] Using lock path: /var/lock/whoopsie/lock Sep 30 11:26:53 non1-MacPro whoopsie[1902]: [11:26:53] The default IPv4 route is: /org/freedesktop/> Sep 30 11:26:53 non1-MacPro whoopsie[1902]: [11:26:53] Not a paid data plan: /org/freedesktop/Netwo> Sep 30 11:26:53 non1-MacPro whoopsie[1902]: [11:26:53] Found usable connection: /org/freedesktop/Ne> Sep 30 11:32:32 non1-MacPro whoopsie[1902]: [11:32:32] Parsing /var/crash/_usr_libexec_ayatana-indi> Sep 30 11:32:32 non1-MacPro whoopsie[1902]: [11:32:32] Uploading /var/crash/_usr_libexec_ayatana-in> Sep 30 11:32:33 non1-MacPro whoopsie[1902]: [11:32:33] Sent; server replied with: No error Sep 30 11:32:33 non1-MacPro whoopsie[1902]: [11:32:33] Response code: 200 Sep 30 11:32:33 non1-MacPro whoopsie[1902]: [11:32:33] Reported OOPS ID 4e2fc590-034b-11eb-bd50-fa1> ~ [CODE/] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Tue, Sep 29 2020, Brian Murray wrote: > On Tue, Sep 29, 2020 at 12:38:38PM -, Nicolas Bock wrote: > Could you please run 'systemctl status whoopsie' and > include the output of the command here? $ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-09-29 06:27:06 MDT; 10h ago Main PID: 2686 (whoopsie) Tasks: 3 (limit: 47889) Memory: 5.0M CGroup: /system.slice/whoopsie.service └─2686 /usr/bin/whoopsie -f Sep 29 08:18:55 rubberducky whoopsie[2686]: [08:18:55] offline Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] online Sep 29 08:59:15 rubberducky whoopsie[2686]: [08:59:15] offline Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] online -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 -, 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Mon, Sep 28, 2020 at 04:51:27AM -, Rocko wrote: > I'm still seeing this bug with apport 2.20.11-0ubuntu48 and systemd > 246.5-1ubuntu1. Do we need systemd 246.6 before it is fixed? I ran 'sudo apt-get dist-upgrade' on a system running groovy and still saw this issue as whoopsie was not able to contact the server to upload the crash report and create the .uploaded file. You could see if this is happening to you by running 'sudo systemctl status whoopsie'. I rebooted and then whoopsie was able to contact the server and the .uploaded file was created and then the .crash file was removed. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 25, 2020 at 07:13:52PM -, Nicolas Bock wrote: > On Fri, Sep 25 2020, Brian Murray wrote: > > > The issue with PathChanged is that /var/crash is used for writing three > > types of files. The .crash file, the .upload file (which signifies the > > crash is ready to be uploaded), and the .uploaded file (which contains > > the UUID of the crash in the error tracker and indicates the crash has > > been uploaded). So if PathChanged is used then whoopsie-upload-all will > > be called for .upload and .uploaded files. Additionally, there is no > > PathChangedGlob so that we could watch for just .crash files. > > Thanks, that makes sense. Although re-reading the > systemd.path manpage over again I still don't understand how > this ever worked. It says: > > "PathExists= may be used to watch the mere existence of a > file or directory. If the file specified exists, the > configured unit is activated." > > I read this as saying that the current behavior on Groovy is > actually correct. Or am I missing something? A bug was fixed in systemd that resolved a discrepancy between what the documentation said (which you've quoted) and the actual behavior of systemd. This is documented upstream in the following issue: https://github.com/systemd/systemd/issues/16669 -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 25 2020, Brian Murray wrote: > The issue with PathChanged is that /var/crash is used for writing three > types of files. The .crash file, the .upload file (which signifies the > crash is ready to be uploaded), and the .uploaded file (which contains > the UUID of the crash in the error tracker and indicates the crash has > been uploaded). So if PathChanged is used then whoopsie-upload-all will > be called for .upload and .uploaded files. Additionally, there is no > PathChangedGlob so that we could watch for just .crash files. Thanks, that makes sense. Although re-reading the systemd.path manpage over again I still don't understand how this ever worked. It says: "PathExists= may be used to watch the mere existence of a file or directory. If the file specified exists, the configured unit is activated." I read this as saying that the current behavior on Groovy is actually correct. Or am I missing something? > To help with the issue I'm working on a change to whoopsie-upload-all to > remove the .crash file after a .uploaded file exists. Thanks! I think this certainly should help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 25, 2020 at 03:42:00PM -, Nicolas Bock wrote: > @balint I was wondering why we don't use `PathChanged` in the systemd > path file. This checks for any changes in the path and will pick up new > crash files... But after reading the systemd docs again I guess the > reason is that we want the service to activate if the crash directory > already contains a crash file on startup. Am I understanding this > correctly? The issue with PathChanged is that /var/crash is used for writing three types of files. The .crash file, the .upload file (which signifies the crash is ready to be uploaded), and the .uploaded file (which contains the UUID of the crash in the error tracker and indicates the crash has been uploaded). So if PathChanged is used then whoopsie-upload-all will be called for .upload and .uploaded files. Additionally, there is no PathChangedGlob so that we could watch for just .crash files. To help with the issue I'm working on a change to whoopsie-upload-all to remove the .crash file after a .uploaded file exists. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 18, 2020 at 08:56:29PM -, Nicolas Bock wrote: > When I run the whoopsie upload script I get: > > $ sudo /usr/share/apport/whoopsie-upload-all > /var/crash/_usr_bin_emacs-gtk.1000.crash already marked for upload, skipping > All reports processed > > Why is it skipping the crash? whoopsie-upload-all checks for a corresponding .uploaded file for the crash report and if it exists that means the crash has already been reported. So if every .crash has a .uploaded file then whoopsie-upload-all does nothing. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 18, 2020 at 09:18:25PM -, Nicolas Bock wrote:
> After deleting the files *.upload{,ed} I can run
>
> $ sudo /usr/share/apport/whoopsie-upload-all
> /var/crash/_usr_bin_emacs-gtk.1000.crash already has info collected
> Marking /var/crash/_usr_bin_emacs-gtk.1000.crash for whoopsie upload
> All reports processed
>
> And get the two files back. The content of the uploaded file is
>
> $ sudo cat _usr_bin_emacs-gtk.1000.uploaded
> 1c9b8196-f9f4-11ea-b6f1-fa163ee63de6
There is an apport cronjob, /etc/cron.daily/apport, which removes
crashes which are older than a week. If I recall correctly this predates
sending crash reports to the Ubuntu Error Tracker and
whoopsie-upload-all. So it'd make sense to have whoopsie-upload-all
remove the .crash and .upload files after the upload succeeded.
However, this is still something goofy going on with systemd.
--
Brian Murray
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
