[Bug 1117217] New: ypbind (NIS) is not started automatically although configured to do so tumbleweed snapshot 20181120
http://bugzilla.opensuse.org/show_bug.cgi?id=1117217 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: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1117217 http://bugzilla.opensuse.org/show_bug.cgi?id=1117217#c1 --- Comment #1 from Walter Obermiller <obermiller@schweizerbart.de> --- Some more information about the ypbind start failure when the tumbleweed starts up: systemctl status ypbind returns:--------------------------------------------- ● ypbind.service - NIS/YP Clients to NIS Domain Binder Loaded: loaded (/usr/lib/systemd/system/ypbind.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:ypbind(8) Nov 25 16:00:51 reservex systemd[1]: Dependency failed for NIS/YP Clients to NIS Domain Binder. Nov 25 16:00:51 reservex systemd[1]: ypbind.service: Job ypbind.service/start failed with result 'dependency'. ---------------------------------------------------------------------------- running yptest returns:----------------------------------------------------- reservex:~ # yptest Test 1: domainname Configured domainname is "xxxxxxxxxxx.de" Test 2: ypbind Can't communicate with ypbind ypbind procotcol v1 test failed Can't communicate with ypbind ypbind procotcol v2 test failed Use Protocol V1: Use Protocol V2: Use Protocol V3: Can't communicate with ypbind ypbind procotcol v3 test failed Test 3: yp_match WARNING: Internal NIS error (Map passwd.byname, key nobody) Test 4: yp_first WARNING: RPC failure on NIS operation (Map passwd.byname) Test 5: yp_next -- skipped -- Test 6: yp_master WARNING: Internal NIS error (Map passwd.byname) Test 7: yp_order WARNING: Internal NIS error (Map passwd.byname) Test 8: yp_maplist WARNING: Internal NIS error Test 9: yp_all WARNING: Can't bind to server which serves this domain (Map passwd.byname) 6 tests failed ---------------------------------------------------------- after starting ypbind manually as root: systemctl start ypbind.service ypbind is properly started and active systemctl status ypbind.service returns: ----------------------------------- ● ypbind.service - NIS/YP Clients to NIS Domain Binder Loaded: loaded (/usr/lib/systemd/system/ypbind.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2018-11-25 16:12:51 CET; 49s ago Docs: man:ypbind(8) Process: 4030 ExecStartPost=/usr/lib/ypbind/ypbind-systemd-post (code=exited, status=0/SUCCESS) Process: 4025 ExecStartPre=/usr/lib/ypbind/ypbind-systemd-pre (code=exited, status=0/SUCCESS) Main PID: 4027 (ypbind) Status: "Processing requests..." Tasks: 3 (limit: 4915) Memory: 1.3M CGroup: /system.slice/ypbind.service └─4027 /usr/sbin/ypbind -n Nov 25 16:12:51 reservex systemd[1]: Starting NIS/YP Clients to NIS Domain Binder... Nov 25 16:12:51 reservex systemd[1]: Started NIS/YP Clients to NIS Domain Binder. and yptest happily reports away that everything is active: reservex:~ # yptest Test 1: domainname Configured domainname is "xxxxxxxxxxx.de" Test 2: ypbind Use Protocol V1: Used NIS server: 192.168.10.229 Use Protocol V2: Used NIS server: 192.168.10.229 Use Protocol V3: ypbind_nconf: nc_netid: udp nc_semantics: 1 nc_flag: 1 nc_protofmly: 'inet' nc_proto: 'udp' nc_device: '-' nc_nlookups: 0 ypbind_svcaddr: 192.168.10.229:654 ypbind_servername: 192.168.10.229 ypbind_hi_vers: 2 ypbind_lo_vers: 2 ...remaining lines (many) deleted....... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1117217 http://bugzilla.opensuse.org/show_bug.cgi?id=1117217#c2 --- Comment #2 from Walter Obermiller <obermiller@schweizerbart.de> --- The network, btw. is started by wicked, NOT NetworkManager, if this is of any relevance. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com