Leap 15.6: cannot run cockpit

C7NhtpnK · September 30, 2025, 6:44am

Dear all,

I cannot run localhost:9090 in my Mozilla Firefox 140.3.0esr (64-Bit) on openSUSE Leap 15.6.

Install

tulicube:~ # zypper se -s -i cockpit
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version         | Arch   | Repository
---+------------------------+---------+-----------------+--------+--------------------------
i+ | cockpit                | package | 321-bp156.2.9.1 | x86_64 | openSUSE-Update-Backports
i  | cockpit-bridge         | package | 321-bp156.2.9.1 | x86_64 | openSUSE-Update-Backports
i+ | cockpit-networkmanager | package | 321-bp156.2.9.1 | noarch | openSUSE-Update-Backports
i+ | cockpit-packagekit     | package | 321-bp156.2.9.1 | noarch | openSUSE-Update-Backports
i+ | cockpit-selinux        | package | 321-bp156.2.9.1 | noarch | openSUSE-Update-Backports
i+ | cockpit-storaged       | package | 321-bp156.2.9.1 | noarch | openSUSE-Update-Backports
i  | cockpit-system         | package | 321-bp156.2.9.1 | noarch | openSUSE-Update-Backports
i  | cockpit-ws             | package | 321-bp156.2.9.1 | x86_64 | openSUSE-Update-Backports

Protocol

08:24:57 systemd: Failed to listen on Socket for Cockpit Web Service http instance.
08:24:57 (sd-chown): cockpit-wsinstance-https-factory.socket: Failed to resolve user cockpit-ws: No such process

Status

tulicube:~ # systemctl status cockpit.socket
× cockpit.socket - Cockpit Web Service Socket
     Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
     Active: failed (Result: trigger-limit-hit) since Tue 2025-09-30 08:24:57 CEST; 11min ago
   Duration: 1min 22.590s
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
    Process: 2065 ExecStartPost=/usr/share/cockpit/motd/update-motd  localhost (code=exited, status=0/SUCCESS)
    Process: 2073 ExecStartPost=/bin/ln -snf active.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
    Process: 3884 ExecStopPost=/bin/ln -snf inactive.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
        CPU: 54ms

Sep 30 08:23:35 tulicube systemd[1]: Starting Cockpit Web Service Socket...
Sep 30 08:23:35 tulicube systemd[1]: Listening on Cockpit Web Service Socket.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.socket: Trigger limit hit, refusing further activation.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.socket: Failed with result 'trigger-limit-hit'.

tulicube:/home/gunnersson/Schreibtisch # systemctl status cockpit-wsinstance-https-factory.socket
× cockpit-wsinstance-https-factory.socket - Socket for Cockpit Web Service https instance factory
     Loaded: loaded (/usr/lib/systemd/system/cockpit-wsinstance-https-factory.socket; static)
     Active: failed (Result: exit-code) since Tue 2025-09-30 08:24:57 CEST; 17min ago
       Docs: man:cockpit-ws(8)
     Listen: /run/cockpit/wsinstance/https-factory.sock (Stream)
   Accepted: 0; Connected: 0;
        CPU: 376us

Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Socket for Cockpit Web Service https instance factory.
Sep 30 08:24:57 tulicube systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Socket for Cockpit Web Service https instance factory.
Sep 30 08:24:57 tulicube systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Socket for Cockpit Web Service https instance factory.
Sep 30 08:24:57 tulicube systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Socket for Cockpit Web Service https instance factory.
Sep 30 08:24:57 tulicube systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Socket for Cockpit Web Service https instance factory.
Sep 30 08:24:57 tulicube systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.

Any idea? Any help? TIA!

deano_ferrari · September 30, 2025, 6:48am

Show the results from sudo journalctl -u cockpit.service -b --no-pager

hui · September 30, 2025, 6:48am

https://bugzilla.opensuse.org/show_bug.cgi?id=1242179

deano_ferrari · September 30, 2025, 6:56am

FWIW, I haven’t run into any issues with cockpit on Leap 15.6, but I installed version from cockpit-project.org repo…

29 | systemsmanagement_cockpit       | cockpit-project.org (15.6)                   | Yes     | (r ) Yes  | No      | -    |   99     | rpm-md | https://download.opensuse.org/repositories/systemsmanagement:/cockpit/15.6/                    

# zypper se -si cockpit
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version        | Arch   | Repository
---+------------------------+---------+----------------+--------+---------------------------
i+ | cockpit                | package | 340-lp156.15.1 | x86_64 | cockpit-project.org (15.6)
i+ | cockpit-bridge         | package | 340-lp156.15.1 | noarch | cockpit-project.org (15.6)
i+ | cockpit-file-sharing   | package | 4.2.10-3.el9   | noarch | (System Packages)
i  | cockpit-firewalld      | package | 340-lp156.15.1 | noarch | cockpit-project.org (15.6)
i+ | cockpit-networkmanager | package | 340-lp156.15.1 | noarch | cockpit-project.org (15.6)
i+ | cockpit-packagekit     | package | 340-lp156.15.1 | noarch | cockpit-project.org (15.6)
i+ | cockpit-storaged       | package | 340-lp156.15.1 | noarch | cockpit-project.org (15.6)
i+ | cockpit-system         | package | 340-lp156.15.1 | noarch | cockpit-project.org (15.6)
i+ | cockpit-ws             | package | 340-lp156.15.1 | x86_64 | cockpit-project.org (15.6)

Sauerland · September 30, 2025, 7:00am

For me the problem was with the /etc/nsswitch.conf not having all entries as described in the bugreport.

deano_ferrari · September 30, 2025, 7:03am

Yes, I edited nsswitch.conf post installation from memory.

Similar described here…

C7NhtpnK · September 30, 2025, 8:47am

tulicube:~ # journalctl -u cockpit.service -b --no-pager
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 30 08:24:57 tulicube systemd[1]: Dependency failed for Cockpit Web Service.
Sep 30 08:24:57 tulicube systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.

C7NhtpnK · September 30, 2025, 8:49am

tulicube:/etc # cat nsswitch.conf
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
#       compat                  Use compatibility setup
#       nisplus                 Use NIS+ (NIS version 3)
#       nis                     Use NIS (NIS version 2), also called YP
#       dns                     Use DNS (Domain Name Service)
#       files                   Use the local files
#       [NOTFOUND=return]       Stop searching if not found so far
#
# For more information, please read the nsswitch.conf.5 manual page.
#

passwd: files usrfiles
group:  files usrfiles
shadow: compat

hosts:  	files mdns_minimal [NOTFOUND=return] dns
networks:	files dns

services:	files
protocols:	files
rpc:		files
ethers:		files
netmasks:	files
netgroup:	files nis
publickey:	files

bootparams:	files
automount:	files nis
aliases:	files

tulicube:/etc # cat nsswitch.conf.nss_usrfiles 
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
#       compat                  Use compatibility setup
#       nisplus                 Use NIS+ (NIS version 3)
#       nis                     Use NIS (NIS version 2), also called YP
#       dns                     Use DNS (Domain Name Service)
#       files                   Use the local files
#       [NOTFOUND=return]       Stop searching if not found so far
#
# For more information, please read the nsswitch.conf.5 manual page.
#

passwd: files usrfiles
group:  files usrfiles
shadow: compat

hosts:  	files mdns_minimal [NOTFOUND=return] dns
networks:	files dns

services:	files
protocols:	files
rpc:		files
ethers:		files
netmasks:	files
netgroup:	files nis
publickey:	files

bootparams:	files
automount:	files nis
aliases:	files

tulicube:/usr/etc # my_ls
total 12K
drwxr-xr-x  3 root root 4.0K Apr  1 11:30 ./
drwxr-xr-x 13 root root 4.0K Mar 15  2022 ../
drwxr-xr-x  2 root root 4.0K Apr 23 00:28 vpl/

deano_ferrari · September 30, 2025, 8:50am

See the advice re nsswitch.conf outlined in the links already given.

C7NhtpnK · September 30, 2025, 8:52am

I am not quite sure…

Delete it or modify it?

Sauerland · September 30, 2025, 9:02am

There are some links given in this Thread for you, you could read them…

The actual proposed fix (and also quick) is to change the /etc/nsswitch.conf to include

passwd:         compat systemd
group:          compat [SUCCESS=merge] systemd
shadow:         compat systemd

to make the systemd dynamic users work on Leap, same as on Tumbleweed. See https://bugzilla.suse.com/show_bug.cgi?id=1230638

C7NhtpnK · September 30, 2025, 11:53am

I am actually begging for detailed help. Sorry for any inconvenience.

Should I modify either /etc/nsswitch.conf or /etc/nsswitch.conf.nss_usrfiles?
I.e. can I leave /etc/nsswitch.conf untouched and just modify /etc/nsswitch.conf.nss_usrfiles?
How to modify it/them? Just use sudo nano or such?
Do I have to replace

passwd: files usrfiles
group:  files usrfiles
shadow: compat

with

passwd:         compat systemd
group:          compat [SUCCESS=merge] systemd
shadow:         compat systemd

?
5. Or could I add

passwd:         compat systemd
group:          compat [SUCCESS=merge] systemd
shadow:         compat systemd

in addition to

passwd: files usrfiles
group:  files usrfiles
shadow: compat

?

I did read the links posted, yes Sir. But these details above haven’t been clear to me. Sorry for being so humble.

Thank you for your help, sirs!

Sauerland · September 30, 2025, 12:08pm

Use a text editor of your choice (nano, vi, also kate or similar) as root.

You have 2 choices:

copy the original file to a backup file:
sudo cp /etc/nsswitch.conf /etc/nsswitch.conf.bak
and replace the original lines in /etc/nsswitch.conf with:

passwd:         compat systemd
group:          compat [SUCCESS=merge] systemd
shadow:         compat systemd

you can modify /etc/nsswitch.conf and mark the lines as comment and add the new lines:

# Bug in Cockpit, replaced at 20250930
#passwd: files usrfiles
#group:  files usrfiles
#shadow: compat

#bug in Cockpit replaced by adding
passwd:         compat systemd
group:          compat [SUCCESS=merge] systemd
shadow:         compat systemd
#endofbug

On both you can revert it.

myswtest · September 30, 2025, 12:26pm

I took the easy route (Flatpak version). I started up the Discover app, clicked on the Cockpit Client entry (Flatpak), then clicked “Install”. 60 seconds later, I’m running it no issues.

C7NhtpnK · September 30, 2025, 12:55pm

Thank you so much!

But before modifying, I have a further question…

tulicube:/etc # my_ls nsswitch*
-rw-r--r-- 1 root root 1.2K Aug 30  2023 nsswitch.conf
-rw-r--r-- 1 root root 1.2K Jun 10  2022 nsswitch.conf.nss_usrfiles
-rw-r--r-- 1 root root 2.2K Dec  3  2024 nsswitch.conf.rpmnew
-rw-r--r-- 1 root root 1.2K Aug 13  2020 nsswitch.confbak

tulicube:/etc # cat nsswitch.conf
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
#       compat                  Use compatibility setup
#       nisplus                 Use NIS+ (NIS version 3)
#       nis                     Use NIS (NIS version 2), also called YP
#       dns                     Use DNS (Domain Name Service)
#       files                   Use the local files
#       [NOTFOUND=return]       Stop searching if not found so far
#
# For more information, please read the nsswitch.conf.5 manual page.
#

passwd: files usrfiles
group:  files usrfiles
shadow: compat

hosts:  	files mdns_minimal [NOTFOUND=return] dns
networks:	files dns

services:	files
protocols:	files
rpc:		files
ethers:		files
netmasks:	files
netgroup:	files nis
publickey:	files

bootparams:	files
automount:	files nis
aliases:	files

tulicube:/etc # cat nsswitch.conf.nss_usrfiles 
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
#       compat                  Use compatibility setup
#       nisplus                 Use NIS+ (NIS version 3)
#       nis                     Use NIS (NIS version 2), also called YP
#       dns                     Use DNS (Domain Name Service)
#       files                   Use the local files
#       [NOTFOUND=return]       Stop searching if not found so far
#
# For more information, please read the nsswitch.conf.5 manual page.
#

passwd: files usrfiles
group:  files usrfiles
shadow: compat

hosts:  	files mdns_minimal [NOTFOUND=return] dns
networks:	files dns

services:	files
protocols:	files
rpc:		files
ethers:		files
netmasks:	files
netgroup:	files nis
publickey:	files

bootparams:	files
automount:	files nis
aliases:	files

tulicube:/etc # cat nsswitch.conf.rpmnew 
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# Valid databases are: aliases, ethers, group, gshadow, hosts,
# initgroups, netgroup, networks, passwd, protocols, publickey,
# rpc, services, and shadow.
#
# Valid service provider entries include (in alphabetical order):
#
#	compat			Use /etc files plus *_compat pseudo-db
#	db			Use the pre-processed /var/db files
#	dns			Use DNS (Domain Name Service)
#	files			Use the local files in /etc
#	hesiod			Use Hesiod (DNS) for user lookups
#	nis			Use NIS (NIS version 2), also called YP
#	nisplus			Use NIS+ (NIS version 3)
#
# See `info libc 'NSS Basics'` for more information.
#
# Commonly used alternative service providers (may need installation):
#
#	ldap			Use LDAP directory server
#	myhostname		Use systemd host names
#	mymachines		Use systemd machine names
#	mdns*, mdns*_minimal	Use Avahi mDNS/DNS-SD
#	resolve			Use systemd resolved resolver
#	sss			Use System Security Services Daemon (sssd)
#	systemd			Use systemd for dynamic user option
#	winbind			Use Samba winbind support
#	wins			Use Samba wins support
#	wrapper			Use wrapper module for testing
#
# Notes:
#
# 'sssd' performs its own 'files'-based caching, so it should generally
# come before 'files'.
#
# WARNING: Running nscd with a secondary caching service like sssd may
# 	   lead to unexpected behaviour, especially with how long
# 	   entries are cached.
#
# Installation instructions:
#
# To use 'db', install the appropriate package(s) (provide 'makedb' and
# libnss_db.so.*), and place the 'db' in front of 'files' for entries
# you want to be looked up first in the databases, like this:
#
# passwd:    db files
# shadow:    db files
# group:     db files

passwd:		compat
group:		compat
shadow:		compat
# Allow initgroups to default to the setting for group.
# initgroups:	compat

hosts:  	files dns
networks:	files dns

aliases:	files usrfiles
ethers:		files usrfiles
gshadow:	files usrfiles
netgroup:	files nis
protocols:	files usrfiles
publickey:	files
rpc:		files usrfiles
services:	files usrfiles

automount:	files nis
bootparams:	files
netmasks:	files

tulicube:/etc # cat nsswitch.confbak 
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
#       compat                  Use compatibility setup
#       nisplus                 Use NIS+ (NIS version 3)
#       nis                     Use NIS (NIS version 2), also called YP
#       dns                     Use DNS (Domain Name Service)
#       files                   Use the local files
#       [NOTFOUND=return]       Stop searching if not found so far
#
# For more information, please read the nsswitch.conf.5 manual page.
#

passwd: compat
group:  compat
shadow: compat

hosts:  	files dns
networks:	files dns

services:	files
protocols:	files
rpc:		files
ethers:		files
netmasks:	files
netgroup:	files nis
publickey:	files

bootparams:	files
automount:	files nis
aliases:	files

How to cope with this issue? I.e. are all these files essential? Or could I (safely) delete them and just keep /etc/nsswitch.conf (and modify that)?

And another question… Where does this file originally come from? How can I reset it to openSUSE system standard? And what do the other files mean and what are they for?

Thank you!

Sauerland · September 30, 2025, 1:02pm

/etc/nsswitch.conf is used and written in by many packages, so different Users, different content.

Also it depends on when it was created by which distribution (Upgrade and so on)

It is in the package:

LANG=C zypper wp /etc/nsswitch.conf
Command 'what-provides' is replaced by 'search --provides --match-exact'.
See 'help search' for all available options.
Loading repository data...
Reading installed packages...

S  | Name  | Summary                                            | Type
---+-------+----------------------------------------------------+--------
i+ | glibc | Standard Shared Libraries (from the GNU C Library) | package

My files:

ls -al /etc/nsswitch*
-rw-r--r-- 1 root root 2261 21. Jul 20:44 /etc/nsswitch.conf
-rw-r--r-- 1 root root 2190 27. Jan 2025  /etc/nsswitch.confbak
-rw-r--r-- 1 root root 2190 18. Apr 2024  /etc/nsswitch.conf.nss_usrfiles
-rw-r--r-- 1 root root 2190  3. Dez 2024  /etc/nsswitch.conf.rpmnew

I have changes it in Jul 2025 to get cockpit working.

C7NhtpnK · September 30, 2025, 1:56pm

Thank you for info!

Thank you very much! Appreciated!

I am almost satisfied and ready soon to apply the changes. But just this question still before:

Do you notice the difference in the dates?

Yours:

ls -al /etc/nsswitch*
-rw-r--r-- 1 root root 2261 21. Jul 20:44 /etc/nsswitch.conf
-rw-r--r-- 1 root root 2190 27. Jan 2025  /etc/nsswitch.confbak
-rw-r--r-- 1 root root 2190 18. Apr 2024  /etc/nsswitch.conf.nss_usrfiles
-rw-r--r-- 1 root root 2190  3. Dez 2024  /etc/nsswitch.conf.rpmnew

Mine:

tulicube:/etc # my_ls nsswitch*
-rw-r--r-- 1 root root 1.2K Aug 30  2023 nsswitch.conf
-rw-r--r-- 1 root root 1.2K Jun 10  2022 nsswitch.conf.nss_usrfiles
-rw-r--r-- 1 root root 2.2K Dec  3  2024 nsswitch.conf.rpmnew
-rw-r--r-- 1 root root 1.2K Aug 13  2020 nsswitch.confbak

I am not talking about the specific dates. I mean the strange order of dates of my files. The order of dates of your files looks much more comprehensible (due to changes…).

So, I am still a bit in a fear.

Sauerland · September 30, 2025, 2:10pm

glibc does only install the file, if it is not available.

Mostly if a package have to change something, it will add a new file and do not change it in the file stored in /etc/ (f. e. /etc/nsswitch.conf).

So you get more files with mostly the same name.

That is, why Tumbleweed (and maybe Leap 16.0) switch to /usr/etc/.
files in this directory are global files and will be overwritten by Updates.
You have to copy the file to /etc/ and make your changes there.

Same as with systemd, global is in /usr/lib/systemd/, your changes are made by copying to /etc/systemd/ (or similar) and change it there.

Sauerland · September 30, 2025, 4:13pm

Maybe read here for the /etc/nsswitch.conf:

https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/A7SX5DWWK42VXYM3WTTJJQFV3FD7B5HE/

C7NhtpnK · September 30, 2025, 4:55pm

I am quite ready to adapt the modification soon. — For Leap 15.6

Just out of interest now this one: is Leap 16.0 ready to run Cockpit without problems, i.e. personal modifications on configuration files?

I mean: Cockpit is the new and current “replacement” for YaST. I would expect it to run out-of-box and properly (without work by the user…).