☰

systemd[1]: apport-autoreport.service: 'start-limit-hit' 결과로 실패했습니다.

tag-icon • tag-icon systemd apport
systemd[1]: apport-autoreport.service: 'start-limit-hit' 결과로 실패했습니다.

systemd는 지속적으로 100%를 사용하고 있습니다. 여기가 최고입니다.

top - 19:47:09 up 13 min,  1 user,  load average: 3.26, 2.62, 1.69
Tasks: 306 total,   4 running, 294 sleeping,   0 stopped,   8 zombie
%Cpu(s): 35.5 us, 12.6 sy,  0.0 ni, 51.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  11858.2 total,   5183.4 free,   3433.2 used,   3241.6 buff/cache
MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.   7913.7 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                    
      1 root      20   0  268660 110536   8532 R 100.0   0.9  11:39.36 systemd                                                                                    
    772 message+  20   0   10988   6768   4116 R  46.0   0.1   5:16.01 dbus-daemon                                                                                
    259 root      19  -1  496536 327492 325464 S  16.8   2.7   2:16.95 systemd-journal                                                                            
    796 syslog    20   0  221104   5832   4052 S  13.9   0.0   1:38.00 rsyslogd                                                                                   
    804 root      20   0  103380  93880   7784 S  13.1   0.8   1:34.41 systemd-logind                                                                             
     18 root      20   0       0      0      0 S   0.7   0.0   0:00.55 ksoftirqd/1                                                                                
   1733 root      20   0  352968 130376  83760 S   0.7   1.1   0:25.47 Xorg                                                                                       
   1916 ava       20   0 4008000 272576 117864 S   0.7   2.2   0:32.40 gnome-shell                                                                                
   3877 ava       20   0 2629148 269672 162688 S   0.7   2.2   0:09.53 Web Content

여기 시스템 로그가 있습니다

 sudo tail -n 100 /var/log/syslog
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
Aug 13 19:46:11 kiev systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Start request repeated too quickly.
Aug 13 19:46:11 kiev systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.

여기 dmesg의 일부가 있습니다

[    3.942656] systemd[1]: Inserted module 'autofs4'
[    4.005635] systemd[1]: systemd 246-2ubuntu1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    4.025381] systemd[1]: Detected architecture x86-64.
[    4.046020] systemd[1]: Set hostname to <kiev>.
[    4.132974] systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly.
[    4.137916] systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    4.164397] systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    4.193000] systemd[1]: /lib/systemd/system/gdm.service:30: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

이 문제는 마지막 시스템 업데이트 후에 발생했습니다. 재부팅 및/또는 다른 시스템 업데이트 후에도 마찬가지입니다. 어떤 아이디어가 있습니까?

우분투 20.04

답변1

임시 해결 방법: /var/crash/ 아래의 모든 파일을 삭제합니다. 장기적이거나 중기적인 해결책은 아니지만 처음부터 아무 것도 하지 않는 것보다 낫습니다.

답변2

더 나은 접근 방식은 아래 업데이트를 참조하세요.

그냥 통제불능 서비스 꺼버려apport

sudo systemctl disable apport-autoreport 
#  sudo apt-get purge apport    #  avoid it works yet is too heavy handed
sudo apt-get purge apport-noui

재부팅 후 systemd CPU 사용량은 아직 정상이었습니다.

tracker-miner-fs

다시 재부팅한 후에도 CPU를 100% 사용하고 있어서 발행했습니다.

gsettings set org.freedesktop.Tracker.Miner.Files crawling-interval -2  
gsettings set org.freedesktop.Tracker.Miner.Files enable-monitors false
echo y | LANG=en tracker reset --hard

이제 다 괜찮아졌어

업데이트

파일 편집 /usr/lib/systemd/system/apport-autoreport.path

#  PathExistsGlob=/var/crash/*.crash  #  <-- old bad comment it out

PathChangedGlob=/var/crash/*.crash    #  good new replaces above line

저장 후 발행

sudo systemctl daemon-reload

자세한 내용은 참조 https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657

이 문제가 해결된 지 몇 달 후 아래는 정상적인 일반 상자의 내용입니다(20210812 기준 Ubuntu 20.04).

cat /usr/lib/systemd/system/apport-autoreport.path 

[Unit]
Description=Process error reports when automatic reporting is enabled (file watch)
ConditionPathExists=/var/lib/apport/autoreport

[Path]
PathExistsGlob=/var/crash/*.crash

[Install]
WantedBy=paths.target

관련 정보