Page 1 of 1

[CLOSED] systemd / gkrellm weirdness

PostPosted: Aug 6th, '18, 00:01
by griffin
My Mageia system is behaving in a weird way. gkrellm is stuttering - its resource graphs just cycle forward and then back every other second rather than showing resource utilization continuously. A ps command reveals that there are three (!) copies of systemd running, two of them with subordinate (sd-pam) and gpg-agent processes, and two copies of both dbus-launch and dbus-daemon running. This can't be normal. Before I reboot and hope that this behavior goes away, the output of a ps command is attached below. Any advice to help me diagnose and fix this will be welcome.
Code: Select all
# ps -A --forest
  PID TTY          TIME CMD
    2 ?        00:00:00 kthreadd
    6 ?        00:00:00  \_ mm_percpu_wq
    7 ?        00:00:03  \_ ksoftirqd/0
    8 ?        00:04:44  \_ rcu_sched
    9 ?        00:00:00  \_ rcu_bh
   10 ?        00:00:00  \_ migration/0
   11 ?        00:00:00  \_ cpuhp/0
   12 ?        00:00:00  \_ cpuhp/1
   13 ?        00:00:00  \_ migration/1
   14 ?        00:00:08  \_ ksoftirqd/1
   17 ?        00:00:00  \_ kdevtmpfs
   18 ?        00:00:00  \_ netns
   21 ?        00:00:00  \_ khungtaskd
   22 ?        00:00:00  \_ oom_reaper
   23 ?        00:00:00  \_ writeback
   24 ?        00:00:00  \_ kcompactd0
   25 ?        00:00:00  \_ ksmd
   26 ?        00:00:00  \_ khugepaged
   27 ?        00:00:00  \_ crypto
   28 ?        00:00:00  \_ kintegrityd
   29 ?        00:00:00  \_ kblockd
   30 ?        00:00:00  \_ ata_sff
   31 ?        00:00:00  \_ md
   32 ?        00:00:00  \_ edac-poller
   33 ?        00:00:00  \_ devfreq_wq
   34 ?        00:00:00  \_ watchdogd
   35 ?        00:00:00  \_ kswapd0
   57 ?        00:00:00  \_ kthrotld
   58 ?        00:00:00  \_ kstrp
   65 ?        00:00:00  \_ charger_manager
  130 ?        00:00:00  \_ scsi_eh_0
  131 ?        00:00:00  \_ scsi_tmf_0
  132 ?        00:00:00  \_ scsi_eh_1
  133 ?        00:00:00  \_ scsi_tmf_1
  138 ?        00:00:00  \_ scsi_eh_2
  139 ?        00:00:00  \_ scsi_tmf_2
  140 ?        00:00:00  \_ scsi_eh_3
  141 ?        00:00:00  \_ scsi_tmf_3
  144 ?        00:00:00  \_ scsi_eh_4
  145 ?        00:00:00  \_ scsi_tmf_4
  146 ?        00:00:00  \_ scsi_eh_5
  147 ?        00:00:00  \_ scsi_tmf_5
  150 ?        00:00:00  \_ scsi_eh_6
  151 ?        00:00:00  \_ scsi_tmf_6
  152 ?        00:00:00  \_ scsi_eh_7
  153 ?        00:00:00  \_ scsi_tmf_7
  165 ?        00:00:00  \_ scsi_eh_8
  166 ?        00:00:00  \_ scsi_tmf_8
  167 ?        00:00:00  \_ scsi_eh_9
  168 ?        00:00:00  \_ scsi_tmf_9
  293 ?        00:00:00  \_ ttm_swap
  413 ?        00:00:00  \_ jbd2/sda6-8
  414 ?        00:00:00  \_ ext4-rsv-conver
  442 ?        00:00:00  \_ jbd2/sda10-8
  443 ?        00:00:00  \_ ext4-rsv-conver
  478 ?        00:00:00  \_ ipv6_addrconf
  567 ?        00:00:00  \_ acpi_thermal_pm
  640 ?        00:00:00  \_ jbd2/sda5-8
  641 ?        00:00:00  \_ ext4-rsv-conver
  677 ?        00:00:07  \_ jbd2/sda7-8
  678 ?        00:00:00  \_ ext4-rsv-conver
  707 ?        00:00:02  \_ jbd2/sda9-8
  708 ?        00:00:00  \_ ext4-rsv-conver
  717 ?        00:00:00  \_ jbd2/sda11-8
  718 ?        00:00:00  \_ ext4-rsv-conver
  725 ?        00:00:00  \_ jbd2/sda12-8
  726 ?        00:00:00  \_ ext4-rsv-conver
  728 ?        00:00:00  \_ jbd2/sda13-8
  729 ?        00:00:00  \_ ext4-rsv-conver
 2509 ?        00:00:00  \_ ib-comp-wq
 2511 ?        00:00:00  \_ ib_mcast
 2513 ?        00:00:00  \_ ib_nl_sa_wq
11536 ?        00:00:14  \_ kworker/1:2
 3317 ?        00:00:02  \_ kworker/0:1H
16680 ?        00:00:00  \_ kworker/1:1H
19496 ?        00:00:00  \_ kworker/1:0H
29234 ?        00:00:01  \_ kworker/0:0
 3401 ?        00:00:00  \_ kworker/1:1
 8182 ?        00:00:00  \_ kworker/u8:1
 9131 ?        00:00:00  \_ kworker/u8:2
 9707 ?        00:00:00  \_ kworker/0:2
 9793 ?        00:00:00  \_ kworker/0:2H
 9896 ?        00:00:00  \_ kworker/1:2H
10079 ?        00:00:00  \_ kworker/u8:0
10080 ?        00:00:00  \_ kworker/1:0
10456 ?        00:00:00  \_ kworker/0:1
    1 ?        00:00:02 systemd
  498 ?        00:00:05 systemd-journal
  545 ?        00:00:00 systemd-udevd
  807 ?        00:00:00 systemd-logind
  808 ?        00:00:02 rtkit-daemon
  811 ?        00:00:19 irqbalance
  815 ?        00:00:00 upowerd
  817 ?        00:00:07 gpm
  818 ?        00:00:00 acpid
  832 ?        00:00:00 chronyd
  833 ?        00:00:00 smartd
  834 ?        00:00:03 dbus-daemon
  844 ?        00:00:00 systemd-network
  855 ?        00:00:00 atd
  856 ?        00:00:00 alsactl
  861 ?        00:00:00 avahi-daemon
  930 ?        00:00:00  \_ avahi-daemon
  862 ?        00:01:39 udisksd
  871 ?        00:00:02 rsyslogd
  927 ?        00:00:02 polkitd
 1110 ?        00:00:09 ifplugd
 1156 ?        00:00:09 ifplugd
 1879 ?        00:00:00 cupsd
 1882 ?        00:00:00 xinetd
 1886 ?        00:00:00 crond
 1889 ?        00:00:00 sddm
 1986 tty1     02:20:20  \_ Xorg
 2571 ?        00:00:00  \_ sddm-helper
 2587 ?        00:00:00      \_ startkde
 2744 ?        00:00:00          \_ kwrapper5
 1905 ?        00:00:00 cups-browsed
 2501 ?        00:00:00 mandi
 2536 ?        00:00:00 systemd
 2554 ?        00:00:00  \_ (sd-pam)
 2558 ?        00:00:08  \_ gpg-agent
 2543 ?        00:00:01 master
20886 ?        00:00:00  \_ qmgr
 8834 ?        00:00:00  \_ pickup
 2569 ?        00:00:00 dbus-launch
 2570 ?        00:00:00 dbus-daemon
 2578 ?        00:00:00 systemd
 2581 ?        00:00:00  \_ (sd-pam)
 2585 ?        00:00:08  \_ gpg-agent
 2815 ?        00:01:22  \_ pulseaudio
 2834 ?        00:00:00      \_ gconf-helper
 2646 ?        00:00:00 dbus-launch
 2647 ?        00:00:01 dbus-daemon
 2683 ?        00:00:00 s2u
 2721 ?        00:00:00 start_kdeinit
 2722 ?        00:00:00 kdeinit5
 2723 ?        00:00:03  \_ klauncher
 2726 ?        00:00:27  \_ kded5
 2733 ?        00:00:03  \_ kaccess
 2749 ?        00:00:03  \_ ksmserver
 2763 ?        01:13:03  |   \_ kwin_x11
 2826 ?        00:00:03  \_ org_kde_powerde
 2836 ?        00:03:40  \_ konsole
 2858 pts/0    00:00:00  |   \_ bash
 3791 pts/0    00:00:00  |   |   \_ su
 3808 pts/0    00:00:00  |   |       \_ bash
 3846 pts/0    00:00:00  |   |           \_ journalctl
 2868 pts/1    00:00:00  |   \_ bash
 3857 pts/1    00:00:00  |   |   \_ su
 3871 pts/1    00:00:00  |   |       \_ bash
10609 pts/1    00:00:00  |   |           \_ ps
 2882 pts/2    00:00:00  |   \_ bash
 2895 pts/3    00:00:00  |   \_ bash
 2855 ?        00:47:30  \_ gkrellm
 2997 ?        00:09:27  \_ thunderbird
10197 ?        00:00:24  \_ firefox
10228 ?        00:00:00      \_ kmozillahelper
 2747 ?        00:00:02 kglobalaccel5
 2756 ?        00:00:00 dconf-service
 2759 ?        00:00:00 mission-control
 2773 ?        00:00:02 kscreen_backend
 2781 ?        00:00:11 krunner
 2784 ?        00:30:01 plasmashell
 2792 ?        00:00:02 polkit-kde-auth
 2794 ?        00:00:03 xembedsniproxy
 2817 ?        00:00:00 xsettings-kde
 2820 ?        00:00:12 kactivitymanage
 3018 ?        00:00:04 hp-systray
 3162 ?        00:00:01  \_ hp-systray
 3163 ?        00:00:17      \_ hp-systray
 3027 ?        00:00:50 mgaapplet
 3029 ?        00:29:47 net_applet
 3048 ?        00:00:00 at-spi-bus-laun
 3056 ?        00:00:01  \_ dbus-daemon
 3058 ?        00:00:04 at-spi2-registr
 3392 ?        00:00:00 obexd
 3521 ?        00:00:02 kuiserver5
 3583 ?        00:00:00 gnome-keyring-d
28871 ?        00:00:01 dirmngr
30482 ?        00:00:02 kwalletd5
22617 ?        00:00:02 dnsmasq

Re: systemd / gkrellm weirdness

PostPosted: Aug 6th, '18, 07:14
by jiml8
Your post indicates trouble with gkrellm but provides no info about gkrellm. I personally have two copies of gkrellm running because one copy isn't sufficient to display all the stuff I want to see. They are both working normally. They do sometimes malfunction, but I blame this on kwin-x11; sometimes I have malfunctions in pretty much any individual window.

Here is my systemd situation:
Code: Select all
jiml@dadsbox:jiml> gettask systemd
  675 ?        Ss     2:44 /usr/lib/systemd/systemd-journald
  719 ?        Ss     0:39 /usr/lib/systemd/systemd-udevd
 7906 ?        Ss     0:06 /usr/lib/systemd/systemd --user
16108 ?        Ss     5:49 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
16197 ?        Ss     0:11 /usr/lib/systemd/systemd-logind
16343 ?        Ss     0:10 /usr/lib/systemd/systemd --user
16347 ?        Ss     0:00 /usr/bin/systemd-tty-ask-password-agent --wall
21971 pts/18   S+     0:00 grep --color systemd
28308 ?        Ss     0:06 /usr/lib/systemd/systemd --user


The command gettask is a bash macro that I employ for convenience. It is replace by "ps ax | grep".

Note that I have 3 copies of systemd --user running. My system is behaving normally, so I presume this is normal. Try just killing gkrellm and restarting it and see if the problem goes away.

Re: systemd / gkrellm weirdness

PostPosted: Aug 6th, '18, 12:32
by doktor5000
jiml8 wrote:Note that I have 3 copies of systemd --user running. My system is behaving normally, so I presume this is normal.

Yes it is. Probably one or two for your user, and one for your login manager. Just use ps aux ;)

Re: systemd / gkrellm weirdness

PostPosted: Aug 6th, '18, 18:59
by griffin
So here's the systemd tasks that are running in my system, not including the "grep systemd" process, as expected:
Code: Select all
# ps aux | grep systemd
root       498  0.0  0.8  93360 33984 ?        Ss   Aug05   0:01 /usr/lib/systemd/systemd-journald
root       540  0.0  0.1  36672  4100 ?        Ss   Aug05   0:00 /usr/lib/systemd/systemd-udevd
message+   801  0.0  0.0  24344  4036 ?        Ss   Aug05   0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
systemd+   818  0.0  0.0  13464  2612 ?        Ss   Aug05   0:00 /usr/lib/systemd/systemd-networkd
root       822  0.0  0.0  15440  2516 ?        Ss   Aug05   0:00 /usr/lib/systemd/systemd-logind
sddm      2256  0.0  0.1  36336  4488 ?        Ss   Aug05   0:00 /usr/lib/systemd/systemd --user
me       2285  0.0  0.1  36324  4520 ?        Ss   Aug05   0:00 /usr/lib/systemd/systemd --user

This is apparently normal, aside from the occasional gkrellm weirdness, so I'll close this topic. When gkrellm hiccups and freezes, I'll just kill it and restart it, as suggested.