[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-10-14 Thread Matthieu Clemenceau
** Tags added: fr-691 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-30 Thread Fritz Hudnut
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? > >

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-29 Thread Nicolas Bock
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

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-29 Thread Brian Murray
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. >

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-29 Thread Nicolas Bock
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

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-29 Thread Rocko
systemd 246.6-1ubuntu1 and apport 2.20.11-0ubuntu48 fix this issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-28 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 246.6-1ubuntu1 --- systemd (246.6-1ubuntu1) groovy; urgency=medium [ Dan Streetman ] * Fix resolved.conf Cache= default to match default (LP: #1895418) Files: - debian/patches/lp1895418.patch

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-28 Thread Brian Murray
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

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-27 Thread Rocko
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? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Fritz Hudnut
@Brian M: As you suggest that my or my problem reported likely by Dan van Vugt with my install of Ubuntu-MATE 20.10 had this similar problem of long strings of "Failed to start " items in the TTY and very long boot times . . . wasn't exactly "fixed" by trashing the /var/crash directory as he

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.11-0ubuntu48 --- apport (2.20.11-0ubuntu48) groovy; urgency=medium * data/whoopsie-upload-all: When processing reports if a .crash file already has a corresponding .uploaded file which is newer than the .crash file remove the

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Brian Murray
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

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Nicolas Bock
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

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Brian Murray
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

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-25 Thread Nicolas Bock
@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

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-23 Thread Nicolas Bock
On systemd-246.4-1ubuntu1 the setting PathChangedGlob leads to an error. But I tried the following which seems to work correctly: [Path] # PathExistsGlob=/var/crash/*.crash PathChanged=/var/crash Thanks @rockrequin for the hint! -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-23 Thread Rocko
Also, if you want to reduce the massive size of the journal logs that this bug creates, do something like this: sudo journalctl --rotate sudo journalctl --vacuum-size=100M That second command reduces it to 100 MB, but you can specify larger or smaller sizes. -- You received this bug

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-23 Thread Rocko
Trying again... After reading the linked systemd bug report, I changed /usr/lib/systemd/system/apport-autoreport.path from having PathExistsGlob to PathChangedGlob and ran sudo systemctl daemon-reload, and this seemed to fix the problem: [Unit] Description=Process error reports when automatic

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-23 Thread Rocko
I changed [Path] PathChangedGlob=/var/crash/*.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service:

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-22 Thread Masroor
This is growing my syslog file like crazy. Often running out of space in /var partition (yes, I have a different partition for this). Deleting the files /var/crash/ stops this. Restarts again after a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-22 Thread Scott Stensland
here is output of running journalctl -b -u whoopsie journalctl -b -u apport-autoreport on Ubuntu 20.10 which has same 100% used by systemd ** Attachment added: "output of running journalctl -b -u whoopsie and journalctl -b -u apport-autoreport"

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-22 Thread Balint Reczey
Will be fixed in next systemd upload, in 246.6-1ubuntu1, at least for the systemd part. https://github.com/systemd/systemd/issues/16669 ** Changed in: systemd (Ubuntu Groovy) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => High ** Bug

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-21 Thread Gannet
>Deleting the files in /var/crash (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13) solved the issue for me aswell. Yeah, until rebooting the machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-21 Thread ToxicDragon
Deleting the files in /var/crash (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13) solved the issue for me aswell. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-18 Thread Brian Murray
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

Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-18 Thread Brian Murray
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?

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-18 Thread Nicolas Bock
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

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-18 Thread Nicolas Bock
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? -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-18 Thread Balint Reczey
Apport keeps reshooting apport-autoreport.service as long as there are files like /var/crash/*.crash: # cat /lib/systemd/system/apport-autoreport.path [Unit] Description=Process error reports when automatic reporting is enabled (file watch) ConditionPathExists=/var/lib/apport/autoreport [Path]

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-17 Thread Balint Reczey
** Changed in: systemd (Ubuntu Groovy) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-17 Thread Balint Reczey
** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-16 Thread Rocko
Doesn't systemd normally stop trying to start a service if it fails too often? That's clearly not happening here, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-15 Thread Brian Murray
I actually think this is either a bug with systemd or a change in how it handles the services which apport-autoreport includes. I've tested this by changing /usr/lib/systemd/system/apport-autoreport.service so that it contains the following: ExecStart=/usr/bin/aplay

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-15 Thread Brian Murray
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-15 Thread Brian Murray
** Tags removed: rls-gg-incoming ** Also affects: apport (Ubuntu Groovy) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-14 Thread Nicolas Bock
$ journalctl -b -u apport-autoreport Sep 14 13:01:52 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Collecting info for /var/crash/_usr_bin_gnome-shell.1000.crash... Sep 14 13:02:07

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-14 Thread Nicolas Bock
The error message (the last 3 lines) keep repeating ad infinitum until I manually remove the crash files in /var/crash as Rocky notes in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-14 Thread Brian Murray
The output of both of the following commands would help us sort out what is going on. journalctl -b -u whoopsie journalctl -b -u apport-autoreport Thanks! Additionally, if this happening on a release other than Ubuntu 20.10 please let me know. ** Changed in: apport (Ubuntu) Assignee:

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-14 Thread Rocko
I ran into this and applied the workaround of deleting all the files in /var/crash to stop the journalctl spam and 100% CPU usage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu.

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-09 Thread Gannet
The same shit on 20.10. Syslog becomes bigger in a real time, then it eats all free space on my /home and system becomes completely unusable. $ sudo service whoopsie status [sudo] пароль до eugene: ● whoopsie.service - crash report submission daemon Loaded: loaded

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-07 Thread Brian Murray
** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-06 Thread taff
I am suffering from this problem. Output from 'sudo service whoospie status': ** Attachment added: "whoopsiestatus.txt" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+attachment/5408046/+files/whoopsiestatus.txt -- You received this bug notification because you are a

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-02 Thread Brian Murray
Could somebody actively suffering from this problem include the output of 'sudo service whoopsie status'? Thanks in advance. It's also worth noting that the apport-autoreport.service is provided by the apport-noui package and removing that package would be a better way to work around this problem

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-09-02 Thread Michael Neuffer
I also had to purge apport in order to get this under control. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-15 Thread Aaron Lichtman
This fix, published by the reporter of this bug, worked for me. https://askubuntu.com/a/1267204 I only needed to follow the steps up to the first reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu.

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-15 Thread Aaron Lichtman
$ systemctl status appoprt-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static) Active: activating (start) since Sat 2020-08-15 12:43:54 CDT; 6ms ago TriggeredBy:

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-15 Thread Aaron Lichtman
I am experiencing this issue on Ubuntu 20.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-15 Thread Ilia
CPU usage 100% /var/log/syslog now takes more than 10GiB and grows... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu.

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-14 Thread Scott Stensland
I am seeing this issue on multiple different laptops which I upgraded in past 24 hours from Ubuntu 20.04 to 20.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

2020-08-14 Thread Scott Stensland
** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+attachment/5401491/+files/dmesg_20200814 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu.