Re: Yast Nework Setting hangs during Initializing Network Configuration
Quote:
Originally Posted by
hcvv
It seems that you think this is something everybody experiences. I am not so sure. AFAIK you are the first to report this. And I can not believe that nobody uses YaST > Netwok Settings. I am still on 15.1, thus I can not testify,.
I too did not observe this issue on 15.1. Doing a web search I did fine similar reports in 13.1 but no resolution.
Re: Yast Nework Setting hangs during Initializing Network Configuration
Quote:
Originally Posted by
malcolmlewis
Hi
Just tested here GNOME/Xorg, all good switching between the two via YaST (openSUSE Leap 15.2 qemu). Could be a Wayland issue, the system is all up to date? What graphics card?
Wayland? Yes, it is definitely not ready for prime time so that is certainly possible.
System is totally up to date and a very ordinary desktop system installation, nothing extraneous installed and nothing outside the Leap 15.2 ecosystem
Graphics is AMD RX550.
Except for the observed anomally the system works fine. I only noticed the hang in Yast Network Settings because I knew I could change the setting of interest there quickly (read lazy). Seeing the anomalous behaviour is why I have inquired about it. If it has been observed and has a fix then good. If it seems worth a bug report then ok. If it's just me...no big deal as it has no functional affect on the system that I can see so far unless I switch to wicked.
enjoy...
Re: Yast Nework Setting hangs during Initializing Network Configuration
Recommend collecting more information.
You can view your system logs in real time by first opening a console running the folllowing command and leaving it open before you do whateveryou observe is having a problem. If anything is written to the system log, you will see it
The other thing you might do is run top in another console and observe if anything that's noticeable changes... Maybe a process will be busy, maybe there will be a change in busy processes.
I agree, it shouldn't take more than a minute at most for devices to be detected.
TSU
Re: Yast Nework Setting hangs during Initializing Network Configuration
Quote:
Originally Posted by
tsu2
Recommend collecting more information.
The content of the system log was posted in my initial post. Nothing in the log appears relavant to the hang issue.
Ah yes, lets do some debugging...
Start Yast from the GUI and let's look at the process tree. As would be expected Yast is running.
Code:
user:~/debug> pstree
systemd-+-ModemManager---2*[{ModemManager}]
|-NetworkManager---2*[{NetworkManager}]
|-accounts-daemon---2*[{accounts-daemon}]
|-agetty
|-auditd---{auditd}
|-avahi-daemon
|-chronyd
|-colord---2*[{colord}]
|-cron
|-cupsd
|-dbus-daemon
|-firewalld---{firewalld}
|-fwupd---4*[{fwupd}]
|-gdm-+-gdm-session-wor-+-gdm-wayland-ses-+-gnome-session-b---3*[{gnome-session-b}]
| | | `-2*[{gdm-wayland-ses}]
| | `-2*[{gdm-session-wor}]
| `-2*[{gdm}]
|-gnome-keyring-d---3*[{gnome-keyring-d}]
|-haveged
|-irqbalance---{irqbalance}
|-master-+-pickup
| `-qmgr
|-mcelog
|-nscd---10*[{nscd}]
|-polkitd---7*[{polkitd}]
|-rsyslogd---4*[{rsyslogd}]
|-rtkit-daemon---2*[{rtkit-daemon}]
|-smartd
|-systemd-+-(sd-pam)
| |-at-spi-bus-laun-+-dbus-daemon
| | `-3*[{at-spi-bus-laun}]
| |-at-spi2-registr---2*[{at-spi2-registr}]
| |-2*[dbus-daemon]
| |-dbus-launch
| |-dconf-service---2*[{dconf-service}]
| |-evolution-addre---5*[{evolution-addre}]
| |-evolution-calen---8*[{evolution-calen}]
| |-evolution-sourc---3*[{evolution-sourc}]
| |-gnome-session-b-+-evolution-alarm---5*[{evolution-alarm}]
| | |-gnome-software---3*[{gnome-software}]
| | |-gnome-tweak-too---2*[{gnome-tweak-too}]
| | |-gsd-disk-utilit---2*[{gsd-disk-utilit}]
| | |-tracker-miner-f---4*[{tracker-miner-f}]
| | `-3*[{gnome-session-b}]
| |-gnome-session-c---{gnome-session-c}
| |-gnome-shell-+-Xwayland---19*[{Xwayland}]
| | |-xdg-su---gnomesu-+-gnomesu-pam-bac---yast2---y2controlcenter---12*[{y2controlcenter}]
| | | `-3*[{gnomesu}]
| | `-19*[{gnome-shell}]
| |-gnome-shell-cal---5*[{gnome-shell-cal}]
| |-gnome-terminal--+-bash---pstree
| | `-3*[{gnome-terminal-}]
| |-goa-daemon---3*[{goa-daemon}]
| |-goa-identity-se---2*[{goa-identity-se}]
| |-gsd-a11y-settin---3*[{gsd-a11y-settin}]
| |-gsd-color---3*[{gsd-color}]
| |-gsd-datetime---3*[{gsd-datetime}]
| |-gsd-housekeepin---3*[{gsd-housekeepin}]
| |-gsd-keyboard---3*[{gsd-keyboard}]
| |-gsd-media-keys---3*[{gsd-media-keys}]
| |-gsd-power---3*[{gsd-power}]
| |-gsd-print-notif---2*[{gsd-print-notif}]
| |-gsd-printer---2*[{gsd-printer}]
| |-gsd-rfkill---2*[{gsd-rfkill}]
| |-gsd-screensaver---2*[{gsd-screensaver}]
| |-gsd-sharing---3*[{gsd-sharing}]
| |-gsd-smartcard---4*[{gsd-smartcard}]
| |-gsd-sound---3*[{gsd-sound}]
| |-gsd-wacom---3*[{gsd-wacom}]
| |-gsd-wwan---3*[{gsd-wwan}]
| |-gsd-xsettings---13*[{gsd-xsettings}]
| |-gvfs-afc-volume---3*[{gvfs-afc-volume}]
| |-gvfs-goa-volume---2*[{gvfs-goa-volume}]
| |-gvfs-gphoto2-vo---2*[{gvfs-gphoto2-vo}]
| |-gvfs-mtp-volume---2*[{gvfs-mtp-volume}]
| |-gvfs-udisks2-vo---3*[{gvfs-udisks2-vo}]
| |-gvfsd-+-gvfsd-burn---2*[{gvfsd-burn}]
| | |-gvfsd-trash---2*[{gvfsd-trash}]
| | `-2*[{gvfsd}]
| |-gvfsd-fuse---5*[{gvfsd-fuse}]
| |-gvfsd-metadata---2*[{gvfsd-metadata}]
| |-mission-control---3*[{mission-control}]
| |-pulseaudio-+-gsettings-helpe---3*[{gsettings-helpe}]
| | `-{pulseaudio}
| `-xdg-permission----2*[{xdg-permission-}]
|-systemd-journal
|-systemd-logind
|-systemd-timesyn---{systemd-timesyn}
|-systemd-udevd
|-udisksd---4*[{udisksd}]
|-upowerd---2*[{upowerd}]
`-wpa_supplicant
Start Network Settings (Yast -> System -> Network Settings) initiates the process y2start.
Code:
user:~/debug> pstree
systemd-+-ModemManager---2*[{ModemManager}]
|-NetworkManager---2*[{NetworkManager}]
|-accounts-daemon---2*[{accounts-daemon}]
|-agetty
|-auditd---{auditd}
|-avahi-daemon
|-chronyd
|-colord---2*[{colord}]
|-cron
|-cupsd
|-dbus-daemon
|-firewalld---{firewalld}
|-fwupd---4*[{fwupd}]
|-gdm-+-gdm-session-wor-+-gdm-wayland-ses-+-gnome-session-b---3*[{gnome-session-b}]
| | | `-2*[{gdm-wayland-ses}]
| | `-2*[{gdm-session-wor}]
| `-2*[{gdm}]
|-gnome-keyring-d---3*[{gnome-keyring-d}]
|-haveged
|-irqbalance---{irqbalance}
|-master-+-pickup
| `-qmgr
|-mcelog
|-nscd---10*[{nscd}]
|-polkitd---7*[{polkitd}]
|-rsyslogd---4*[{rsyslogd}]
|-rtkit-daemon---2*[{rtkit-daemon}]
|-smartd
|-systemd-+-(sd-pam)
| |-at-spi-bus-laun-+-dbus-daemon
| | `-3*[{at-spi-bus-laun}]
| |-at-spi2-registr---2*[{at-spi2-registr}]
| |-2*[dbus-daemon]
| |-dbus-launch
| |-dconf-service---2*[{dconf-service}]
| |-evolution-addre---5*[{evolution-addre}]
| |-evolution-calen---8*[{evolution-calen}]
| |-evolution-sourc---3*[{evolution-sourc}]
| |-gnome-session-b-+-evolution-alarm---5*[{evolution-alarm}]
| | |-gnome-software---3*[{gnome-software}]
| | |-gnome-tweak-too---2*[{gnome-tweak-too}]
| | |-gsd-disk-utilit---2*[{gsd-disk-utilit}]
| | |-tracker-miner-f---4*[{tracker-miner-f}]
| | `-3*[{gnome-session-b}]
| |-gnome-session-c---{gnome-session-c}
| |-gnome-shell-+-Xwayland---19*[{Xwayland}]
| | |-xdg-su---gnomesu-+-gnomesu-pam-bac---yast2---y2controlcenter---12*[{y2controlcenter}]
| | | `-3*[{gnomesu}]
| | `-20*[{gnome-shell}]
| |-gnome-shell-cal---5*[{gnome-shell-cal}]
| |-gnome-terminal--+-bash---pstree
| | `-3*[{gnome-terminal-}]
| |-goa-daemon---3*[{goa-daemon}]
| |-goa-identity-se---2*[{goa-identity-se}]
| |-gsd-a11y-settin---3*[{gsd-a11y-settin}]
| |-gsd-color---3*[{gsd-color}]
| |-gsd-datetime---3*[{gsd-datetime}]
| |-gsd-housekeepin---3*[{gsd-housekeepin}]
| |-gsd-keyboard---3*[{gsd-keyboard}]
| |-gsd-media-keys---3*[{gsd-media-keys}]
| |-gsd-power---3*[{gsd-power}]
| |-gsd-print-notif---2*[{gsd-print-notif}]
| |-gsd-printer---2*[{gsd-printer}]
| |-gsd-rfkill---2*[{gsd-rfkill}]
| |-gsd-screensaver---2*[{gsd-screensaver}]
| |-gsd-sharing---3*[{gsd-sharing}]
| |-gsd-smartcard---4*[{gsd-smartcard}]
| |-gsd-sound---3*[{gsd-sound}]
| |-gsd-wacom---3*[{gsd-wacom}]
| |-gsd-wwan---3*[{gsd-wwan}]
| |-gsd-xsettings---13*[{gsd-xsettings}]
| |-gvfs-afc-volume---3*[{gvfs-afc-volume}]
| |-gvfs-goa-volume---2*[{gvfs-goa-volume}]
| |-gvfs-gphoto2-vo---2*[{gvfs-gphoto2-vo}]
| |-gvfs-mtp-volume---2*[{gvfs-mtp-volume}]
| |-gvfs-udisks2-vo---3*[{gvfs-udisks2-vo}]
| |-gvfsd-+-gvfsd-burn---2*[{gvfsd-burn}]
| | |-gvfsd-trash---2*[{gvfsd-trash}]
| | `-2*[{gvfsd}]
| |-gvfsd-fuse---5*[{gvfsd-fuse}]
| |-gvfsd-metadata---2*[{gvfsd-metadata}]
| |-mission-control---3*[{mission-control}]
| |-pulseaudio-+-gsettings-helpe---3*[{gsettings-helpe}]
| | `-{pulseaudio}
| |-xdg-permission----2*[{xdg-permission-}]
| `-yast2---y2start---14*[{y2start}]
|-systemd-journal
|-systemd-logind
|-systemd-timesyn---{systemd-timesyn}
|-systemd-udevd
|-udisksd---4*[{udisksd}]
|-upowerd---2*[{upowerd}]
`-wpa_supplicant
At this point the Network Settings is now hung at the "Initializing Network Configuration" screen at "Read device configuration" and is non-responsive. The process y2start is running so lets take a look.
Code:
user:~/debug> top
top - 15:06:12 up 5 min, 2 users, load average: 0.62, 0.66, 0.37
Tasks: 236 total, 2 running, 234 sleeping, 0 stopped, 0 zombie
%Cpu(s): 25.4 us, 0.1 sy, 0.0 ni, 74.2 id, 0.3 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 14994.47+total, 13418.41+free, 881.703 used, 694.352 buff/cache
MiB Swap: 23999.99+total, 23999.99+free, 0.000 used. 13821.04+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3028 root 20 0 1755132 203412 101636 R 100.0 1.325 0:30.89 y2start
2264 cosmic 20 0 4139172 217676 118508 S 0.997 1.418 0:12.45 gnome-she+
2858 cosmic 20 0 547992 50388 40332 S 0.332 0.328 0:01.37 gnome-ter+
1 root 20 0 221176 10084 7016 S 0.000 0.066 0:09.33 systemd
2 root 20 0 0 0 0 S 0.000 0.000 0:00.00 kthreadd
3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_par_gp
6 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 kworker/0+
7 root 20 0 0 0 0 I 0.000 0.000 0:00.01 kworker/u+
8 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 mm_percpu+
9 root 20 0 0 0 0 S 0.000 0.000 0:00.02 ksoftirqd+
10 root 20 0 0 0 0 I 0.000 0.000 0:00.11 rcu_sched
11 root rt 0 0 0 0 S 0.000 0.000 0:00.00 migration+
12 root -51 0 0 0 0 S 0.000 0.000 0:00.00 idle_inje+
13 root 20 0 0 0 0 I 0.000 0.000 0:00.03 kworker/0+
14 root 20 0 0 0 0 S 0.000 0.000 0:00.00 cpuhp/0
15 root 20 0 0 0 0 S 0.000 0.000 0:00.00 cpuhp/1
The process y2start is running with 100% CPU utilization. Not good, so let's snoop what it is doing.
Code:
user:~/debug> sudo strace -r -p 3028
strace: Process 3028 attached
0.000000 brk(0x5569ec637000) = 0x5569ec637000
21.768048 brk(0x5569ec658000) = 0x5569ec658000
21.675483 brk(0x5569ec679000) = 0x5569ec679000
21.615739 brk(0x5569ec69a000) = 0x5569ec69a000
21.628528 brk(0x5569ec6bb000) = 0x5569ec6bb000
19.241669 brk(0x5569ec6e0000) = 0x5569ec6e0000
0.001210 brk(0x5569ec704000) = 0x5569ec704000
0.001154 brk(0x5569ec728000) = 0x5569ec728000
0.000179 brk(0x5569ec749000) = 0x5569ec749000
0.001547 brk(0x5569ec76c000) = 0x5569ec76c000
0.001185 brk(0x5569ec790000) = 0x5569ec790000
0.001181 brk(0x5569ec7b4000) = 0x5569ec7b4000
0.001190 brk(0x5569ec7d8000) = 0x5569ec7d8000
0.001187 brk(0x5569ec7fc000) = 0x5569ec7fc000
0.000941 brk(0x5569ec846000) = 0x5569ec846000
0.001957 brk(0x5569ec868000) = 0x5569ec868000
0.001192 brk(0x5569ec88c000) = 0x5569ec88c000
0.001191 brk(0x5569ec8b0000) = 0x5569ec8b0000
0.001169 brk(0x5569ec8d4000) = 0x5569ec8d4000
0.001179 brk(0x5569ec8f8000) = 0x5569ec8f8000
0.001188 brk(0x5569ec91c000) = 0x5569ec91c000
0.001189 brk(0x5569ec940000) = 0x5569ec940000
0.009084 brk(0x5569ec99a000) = 0x5569ec99a000
0.015690 brk(0x5569eca09000) = 0x5569eca09000
0.049572 brk(0x5569eca47000) = 0x5569eca47000
0.002079 brk(0x5569ecae7000) = 0x5569ecae7000
0.007581 brk(0x5569ecb87000) = 0x5569ecb87000
0.003878 brk(0x5569ecc77000) = 0x5569ecc77000
0.008849 brk(0x5569eccb9000) = 0x5569eccb9000
428.647183 brk(0x5569eccda000) = 0x5569eccda000
21.469835 brk(0x5569eccfb000) = 0x5569eccfb000
21.475396 brk(0x5569ecd1c000) = 0x5569ecd1c000
21.470280 brk(0x5569ecd3d000) = 0x5569ecd3d000
21.468734 brk(0x5569ecd5e000) = 0x5569ecd5e000
21.479867 brk(0x5569ecd7f000) = 0x5569ecd7f000
21.409221 brk(0x5569ecda0000) = 0x5569ecda0000
21.265440 brk(0x5569ecdc1000) = 0x5569ecdc1000
10.985522 brk(0x5569ece40000) = 0x5569ece40000
0.003199 brk(0x5569ecee7000) = 0x5569ecee7000
0.004947 brk(0x5569ecf76000) = 0x5569ecf76000
0.015022 brk(0x5569ecf98000) = 0x5569ecf98000
0.001297 brk(0x5569ecfbc000) = 0x5569ecfbc000
0.001247 brk(0x5569ecfe0000) = 0x5569ecfe0000
(the output shortened here as it simply continues repeatedly)
Ok, the process y2start is thrashing around readjusting the heap (program break) which it continues to do for a very long, indeterminate time. Eventually it settles and enters the Network Settings screen then appears to work properly. This very much looks to be a bug in the y2start process.
Comments?
enjoy...
Re: Yast Nework Setting hangs during Initializing Network Configuration
Anything interesting reported in y2log?
Re: Yast Nework Setting hangs during Initializing Network Configuration
Quote:
Originally Posted by
deano_ferrari
Anything interesting reported in y2log?
Nothing that is an obvious warning, error or other complaint...looks like ordinary process chatter...but I am not at all familiar with Yast internals.
enjoy...
Re: Yast Nework Setting hangs during Initializing Network Configuration
Filed a bug report on this - bug 1177503.
Thanks to all for your input!
Re: Yast Nework Setting hangs during Initializing Network Configuration
Just a note to close this thread. YaST Network Setting initialization running slow is a know and confirmed "behaviour", "feature" or "bug". It occurs because the /etc/hosts file is parsed and loaded as part of Network Setting initialization. The larger the /etc/hosts file, the longer Network Settings initialization takes and seems to be nlog(n) for Big O fans. Upshot is, if you are using hosts to block domains then you will notice the slow initialization in Network Settings, so just wait.
A better solution to domain blocking is a DNS firewall which is what I was setting up when I stumbled upon this issue with Network Settings. I have implemented the unbound DNS resolver as a DNS firewall using RPZ to replace hosts blocking. Works like a charm. The only caveat is that RPZ is implemented in unbound v1.10 and the version in Leap 15.2 is v1.6. However, Tumbleweed (as of this writing) has a build of unbound v1.12 for Leap 15.2 which works fine.
enjoy...
