Bug ID 1117217
Summary ypbind (NIS) is not started automatically although configured to do so tumbleweed snapshot 20181120
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS SUSE Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter obermiller@schweizerbart.de
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

I have set up a machine yesterday from bare metal using the Tumbleweed 20181120
snapshot medium.

After configuring the machine and all required services (networking) I used
Yast2 to set this machine up as a NIS client, saved everything and rebooted in
order to activate nis, the way this has worked for a number of other machines
before.

However, after rebooting I find that I cannot log in as a nis user and after
logging in as root it turns out that ypbind has obviously not been started,
i.e. yptest reports a number of error messages.

After issuing a systemctl start ypbind.service as root manually, yptest returns
the correct list of data, indicating that YP now works. Logging out and logging
in again as the nis user, everything works as expected.

The question hence is, why ypbind fails to be started at startup (systemd?).

If you need any logs or other information to diagnose further, please don't
hesitate to contact me.


You are receiving this mail because: