Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Oct 2004 17:48:48 GMT
From:      Tony Shadwick <tonys@stg-stl.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   i386/72592: NIS Domain Master fails as client of itself
Message-ID:  <200410121748.i9CHmmdX030007@www.freebsd.org>
Resent-Message-ID: <200410121750.i9CHoUkM042979@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         72592
>Category:       i386
>Synopsis:       NIS Domain Master fails as client of itself
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 12 17:50:30 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Tony Shadwick
>Release:        5.2.1
>Organization:
Strategic Technology Group
>Environment:
FreeBSD zeus.stg-stl.net 5.2.1-RELEASE FreeBSd 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004     root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC    i386
>Description:
When setting up an NIS domain master per FreeBSD's documentation, you are instructed to make a copy of master.passwd in /var/yp, remove any system or administrative accounts and make domain-name, which succeeds.

This leaves you with your users' accounts in both /etc/master.passwd and /var/yp/master.passwd, and if you wish to add a user, you must add to both for the user to be valid on both the domain master and the nis domain.

The solution is to set the system up as an NIS client per FreeBSD's documentation, by adding the following lines to /etc/rc.conf:

nisdomainname="domain-name"
rpcbind_enable="YES"
nis_client_enable="YES"
nis_client_flags="-S domain-name,server1,server2"

Remove the users from /etc/master.passwd that exist in /var/yp/master.passwd, and add +::::::::: at the bottom of /etc/master.passwd.

However, after rebooting with this configuration, the users in /var/yp/master.passwd do not register on the system.  

ypcat passwd
clnttcp_create failed
ypcat: no such map passwd.byname. reason: Can't communicate with portmapper

Connectivity to rpcbind is allowed through /etc/hosts.allow, and there are no active firewall rules.
>How-To-Repeat:
Configure the system per FreeBSD's documentation as an NIS Server, then add to that configuration the steps required to run as a client of itself.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410121748.i9CHmmdX030007>