dbus-daemon сжирает 500 мегабайт оперативки и выше

Аппетиты растут, но сегодня скромнее :)
[wolf@wolf-pc ~]$ systemctl status dbus
● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
     Active: active (running) since Sun 2021-11-28 11:42:55 MSK; 3h 20min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 515 (dbus-daemon)
      Tasks: 1 (limit: 28775)
     Memory: 44.6M
        CPU: 45.626s
     CGroup: /system.slice/dbus.service
             └─515 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

ноя 28 11:44:02 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.57' (uid=1000 pid=1291 >
ноя 28 11:44:02 wolf-pc dbus-daemon[515]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
ноя 28 11:54:37 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' >
ноя 28 11:54:37 wolf-pc dbus-daemon[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
ноя 28 14:26:24 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.66' (uid=1000 pid=1125 >
ноя 28 14:26:24 wolf-pc dbus-daemon[515]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
ноя 28 14:26:36 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' >
ноя 28 14:26:36 wolf-pc dbus-daemon[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
ноя 28 14:54:44 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' >
ноя 28 14:54:44 wolf-pc dbus-daemon[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
RusWolf
сегодня
а в журнале спама нет?
journalctl -f
journalctl -b |grep dbus|grep Rejected
RusWolf
Наконец добрались руки дома, до четвёртого компа с KDE.
B вот на нём наконец случилось чудо :)
Наверное, тебе проще найти виновника - не все же одинаково на 4-х компах ...
Ошибки не исчезают с опытом - они просто умнеют
vs220
journalctl -f
[wolf@wolf-pc ~]$ journalctl -f
-- Journal begins at Sun 2021-11-28 11:42:52 MSK. --
ноя 28 15:34:12 wolf-pc NetworkManager[516]: <info>  [1638102852.5521] dhcp4 (wlp0s19f2u5): state changed unknown -> bound, address=192.168.100.2
ноя 28 15:34:12 wolf-pc NetworkManager[516]: <info>  [1638102852.5539] policy: set 'HUAWEI-Home8' (wlp0s19f2u5) as default for IPv4 routing and DNS
ноя 28 15:34:12 wolf-pc systemd-timesyncd[458]: Network configuration changed, trying to establish connection.
ноя 28 15:34:12 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=516 comm="/usr/bin/NetworkManager --no-daemon ")
ноя 28 15:34:12 wolf-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
ноя 28 15:34:12 wolf-pc dbus-daemon[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
ноя 28 15:34:12 wolf-pc systemd[1]: Started Network Manager Script Dispatcher Service.
ноя 28 15:34:12 wolf-pc systemd-timesyncd[458]: Initial synchronization to time server 5.39.184.5:123 (0.arch.pool.ntp.org).
ноя 28 15:34:13 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
ноя 28 15:34:14 wolf-pc systemd-networkd[498]: wlp0s19f2u5: DHCPv4 address 192.168.100.2/24 via 192.168.100.1
ноя 28 15:34:22 wolf-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
ноя 28 15:34:44 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: Trying to associate with e8:37:7a:95:61:9e (SSID='HUAWEI-Home8' freq=2437 MHz)
ноя 28 15:34:44 wolf-pc systemd-networkd[498]: wlp0s19f2u5: Lost carrier
ноя 28 15:34:44 wolf-pc systemd-networkd[498]: wlp0s19f2u5: DHCP lease lost
ноя 28 15:34:44 wolf-pc wpa_supplicant[617]: nl80211: kernel reports: Authentication algorithm number required
ноя 28 15:34:44 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=2437 ht_enabled=1 ch_offset=1 ch_width=40 MHz cf1=2447 cf2=0
ноя 28 15:34:44 wolf-pc NetworkManager[516]: <info>  [1638102884.9144] device (wlp0s19f2u5): supplicant interface state: completed -> associating
ноя 28 15:34:44 wolf-pc NetworkManager[516]: <info>  [1638102884.9144] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: completed -> associating
ноя 28 15:34:44 wolf-pc NetworkManager[516]: <info>  [1638102884.9146] device (wlp0s19f2u5): DHCPv4 lease renewal requested
ноя 28 15:34:44 wolf-pc NetworkManager[516]: <info>  [1638102884.9147] dhcp4 (wlp0s19f2u5): canceled DHCP transaction
ноя 28 15:34:44 wolf-pc NetworkManager[516]: <info>  [1638102884.9147] dhcp4 (wlp0s19f2u5): state changed bound -> terminated
ноя 28 15:34:44 wolf-pc NetworkManager[516]: <info>  [1638102884.9155] dhcp4 (wlp0s19f2u5): activation: beginning transaction (timeout in 45 seconds)
ноя 28 15:34:44 wolf-pc systemd-networkd[498]: wlp0s19f2u5: DHCPv6 lease lost
ноя 28 15:34:44 wolf-pc systemd-timesyncd[458]: No network connectivity, watching for changes.
ноя 28 15:34:44 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: Associated with e8:37:7a:95:61:9e
ноя 28 15:34:44 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
ноя 28 15:34:44 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=RU
ноя 28 15:34:45 wolf-pc NetworkManager[516]: <info>  [1638102885.0032] device (wlp0s19f2u5): supplicant interface state: associating -> associated
ноя 28 15:34:45 wolf-pc NetworkManager[516]: <info>  [1638102885.0033] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: associating -> associated
ноя 28 15:34:54 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: Authentication with e8:37:7a:95:61:9e timed out.
ноя 28 15:34:55 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-DISCONNECTED bssid=e8:37:7a:95:61:9e reason=3 locally_generated=1
ноя 28 15:34:55 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
ноя 28 15:34:55 wolf-pc NetworkManager[516]: <info>  [1638102895.0116] device (wlp0s19f2u5): supplicant interface state: associated -> disconnected
ноя 28 15:34:55 wolf-pc NetworkManager[516]: <info>  [1638102895.0117] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: associated -> disconnected
ноя 28 15:34:55 wolf-pc NetworkManager[516]: <info>  [1638102895.1115] device (wlp0s19f2u5): supplicant interface state: disconnected -> scanning
ноя 28 15:34:55 wolf-pc NetworkManager[516]: <info>  [1638102895.1115] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: disconnected -> scanning
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: Trying to associate with 04:9f:ca:a1:b6:34 (SSID='HUAWEI-Home8' freq=2437 MHz)
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: nl80211: kernel reports: Authentication algorithm number required
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=2437 ht_enabled=1 ch_offset=0 ch_width=20 MHz cf1=2437 cf2=0
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.3967] device (wlp0s19f2u5): supplicant interface state: scanning -> associating
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.3968] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: scanning -> associating
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: Associated with 04:9f:ca:a1:b6:34
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5308] device (wlp0s19f2u5): supplicant interface state: associating -> associated
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5308] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: associating -> associated
ноя 28 15:34:59 wolf-pc systemd-udevd[4488]: regulatory.0: Process '/usr/bin/crda' failed with exit code 234.
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5309] device (wlp0s19f2u5): DHCPv4 lease renewal requested
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: WPA: Key negotiation completed with 04:9f:ca:a1:b6:34 [PTK=CCMP GTK=TKIP]
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-CONNECTED - Connection to 04:9f:ca:a1:b6:34 completed [id=0 id_str=]
ноя 28 15:34:59 wolf-pc wpa_supplicant[617]: bgscan simple: Failed to enable signal strength monitoring
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5492] dhcp4 (wlp0s19f2u5): canceled DHCP transaction
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5493] dhcp4 (wlp0s19f2u5): state changed unknown -> terminated
ноя 28 15:34:59 wolf-pc systemd-networkd[498]: wlp0s19f2u5: Gained carrier
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5501] dhcp4 (wlp0s19f2u5): activation: beginning transaction (timeout in 45 seconds)
ноя 28 15:34:59 wolf-pc systemd-timesyncd[458]: Network configuration changed, trying to establish connection.
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5514] device (wlp0s19f2u5): supplicant interface state: associated -> 4way_handshake
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5515] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: associated -> 4way_handshake
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5577] device (wlp0s19f2u5): supplicant interface state: 4way_handshake -> completed
ноя 28 15:34:59 wolf-pc NetworkManager[516]: <info>  [1638102899.5578] device (p2p-dev-wlp0s19f2u5): supplicant management interface state: 4way_handshake -> completed
ноя 28 15:35:00 wolf-pc systemd-timesyncd[458]: Network configuration changed, trying to establish connection.
ноя 28 15:35:00 wolf-pc NetworkManager[516]: <info>  [1638102900.4340] policy: set 'HUAWEI-Home8' (wlp0s19f2u5) as default for IPv6 routing and DNS
ноя 28 15:35:01 wolf-pc NetworkManager[516]: <info>  [1638102901.5797] dhcp4 (wlp0s19f2u5): state changed unknown -> bound, address=192.168.100.2
ноя 28 15:35:01 wolf-pc NetworkManager[516]: <info>  [1638102901.5805] policy: set 'HUAWEI-Home8' (wlp0s19f2u5) as default for IPv4 routing and DNS
ноя 28 15:35:01 wolf-pc systemd-timesyncd[458]: Network configuration changed, trying to establish connection.
ноя 28 15:35:01 wolf-pc dbus-daemon[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=516 comm="/usr/bin/NetworkManager --no-daemon ")
ноя 28 15:35:01 wolf-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
ноя 28 15:35:01 wolf-pc dbus-daemon[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
ноя 28 15:35:01 wolf-pc systemd[1]: Started Network Manager Script Dispatcher Service.
ноя 28 15:35:02 wolf-pc wpa_supplicant[617]: wlp0s19f2u5: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
ноя 28 15:35:03 wolf-pc systemd-networkd[498]: wlp0s19f2u5: DHCPv4 address 192.168.100.2/24 via 192.168.100.1
ноя 28 15:35:03 wolf-pc systemd-timesyncd[458]: Network configuration changed, trying to establish connection.
ноя 28 15:35:03 wolf-pc systemd-timesyncd[458]: Network configuration changed, trying to establish connection.
ноя 28 15:35:11 wolf-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
vs220
journalctl -b |grep dbus|grep Rejected
[wolf@wolf-pc ~]$ journalctl -b  | grep dbus | grep Rejected
[wolf@wolf-pc ~]$
RusWolf
journalctl -f
это вывод журнала в режиме реального времени
имелось в ввиду нет ли там постоянного вывода каких то событий
vs220
имелось в ввиду нет ли там постоянного вывода каких то событий
Нет.
[wolf@wolf-pc ~]$ systemctl status dbus
● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
     Active: active (running) since Sun 2021-11-28 11:42:55 MSK; 9h ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 515 (dbus-daemon)
      Tasks: 1 (limit: 28775)
     Memory: 210.6M
        CPU: 4min 24.016s
     CGroup: /system.slice/dbus.service
             └─515 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Пока так.

[wolf@wolf-pc ~]$ systemctl status dbus
● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
     Active: active (running) since Sun 2021-11-28 11:42:55 MSK; 11h ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 515 (dbus-daemon)
      Tasks: 1 (limit: 28775)
     Memory: 338.2M
        CPU: 6min 29.289s
     CGroup: /system.slice/dbus.service
             └─515 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
Пока на этом и остановился.
И все-таки хорошо бы точно узнать где сидит эта увеличивающаяся память - в кэше или нет?
Сколько сидит ее в кэше можно узнать следующим образом
- определяем сколько набежало: systemctl status dbus | grep Memory .... Memory: 4.1M
- скидываем весь кэш: sync && echo 3 | sudo tee /proc/sys/vm/drop_caches
- определяем сколько осталось: systemctl status dbus | grep Memory .... Memory: 2.9M
Высчитываем сколько кэша скинулось: 4,1 - 2,9 = 1,2M

PS - nafanja раньше проделывал это, но скинул не весь кэш (echo 1 | sudo tee /proc/sys/vm/drop_caches), просто я так посоветовал и прописывая 1 у него особо и не скинулось, ... а вот про 3 не стал сразу напоминать.
Ошибки не исчезают с опытом - они просто умнеют
vasek
systemctl status dbus | grep Memory
Memory: 58.0M

[wolf@wolf-pc ~]$ sync && echo 3 | sudo tee /proc/sys/vm/drop_caches
[sudo] пароль для wolf:
3

[wolf@wolf-pc ~]$ systemctl status dbus | grep Memory
     Memory: 57.1M

58.0M - 57.1M = с гулькин нос.
RusWolf
58.0M - 57.1M = с гулькин нос.
все относительно, а в принципе тоже самое: vasek -1,2M, RusWolf -0.9М, nafanja -2.4M )))
ВЫВОД: утечка не связана с кэшем вообще!
Псевдографический инсталлятор Arch Linux ver. 3.8.2
Благодарности принимаются на ЯД 410012815723874
 
Зарегистрироваться или войдите чтобы оставить сообщение.