Sponsored Content
Operating Systems Solaris Error while configuring NIS master Post 302552911 by manju-- on Tuesday 6th of September 2011 05:16:19 AM
Old 09-06-2011
Error while configuring NIS master

Hello - I have a Solaris machine, which I would like to configure as NIS master. When I run the command /usr/sbin/ypinit -m, I see below output. I am enclosing them in tags.
Code:
 /usr/sbin/ypinit -m

In order for NIS to operate sucessfully, we have to construct a list of the
NIS servers.  Please continue to add the names for YP servers in order of
preference, one per line.  When you are done with the list, type a <control D>
or a return on a line by itself.
        next host to add:  idm187-05
        next host to add:  ^D
The current list of yp servers looks like this:

idm187-05

Is this correct?  [y/n: y]  y

Installing the YP database will require that you answer a few questions.
Questions will all be asked at the beginning of the procedure.

Do you want this procedure to quit on non-fatal errors? [y/n: n]  y
The yp domain directory is /var/yp/connectortest.oracle.com
Can we destroy the existing /var/yp/connectortest.oracle.com and its contents? [y/n: n]  y
There will be no further questions. The remainder of the procedure should take
5 to 10 minutes.
Building /var/yp/connectortest.oracle.com/ypservers...
Running /var/yp /Makefile...
updated passwd
updated group
updated hosts
updated ipnodes
updated ethers
updated networks
updated rpc
updated services
updated protocols
updated netgroup
updated bootparams
/etc/mail/sendmail.cf: WARNING: dangerous write permissions
/etc/mail/sendmail.cf: line 80: fileclass: cannot open '/etc/mail/local-host-names': World writable directory
/etc/mail/sendmail.cf: line 561: fileclass: cannot open '/etc/mail/trusted-users': World writable directory
WARNING: local host name (idm187-05) is not qualified; see cf/README: WHO AM I?
*** Error code 71
The following command caused the error:
/usr/lib/sendmail -bi -oA/var/yp/`domainname`/mail.aliases;
updated publickey
updated netid
/usr/sbin/makedbm /etc/netmasks /var/yp/`domainname`/netmasks.byaddr;
updated netmasks
updated passwd.adjunct
updated timezone
updated auto.master
updated auto.home
updated ageing
updated auth_attr
updated exec_attr
updated prof_attr
updated user_attr
updated audit_user
make: Warning: Target `all' not remade because of errors
Current working directory /var/yp
*** Error code 1
The following command caused the error:
if [ ! 1 ]; then make   -k all; \
else make  -k all NOPUSH=1;fi
make: Fatal error: Command failed for target `k'
Error running Makefile.

Please let me know what could be the issue.
 

9 More Discussions You Might Find Interesting

1. Solaris

configuring SMC to work with NIS

hello, after couple days trying to configure SMC to work with NIS on Solaris 8, i gave up...have any of you have done it before? what change did you make when you edited the toolbox? also, when you create a new toolbox, they ask for server and domain, what do you have to fill into these two... (0 Replies)
Discussion started by: hlude92
0 Replies

2. UNIX for Advanced & Expert Users

NIS master / slave problems

Our NIS master server went down. We have since fixed it and brought it back up. However all of are machines still point to the slave server when looking at it with ypwhich. My question is how do i point the servers back to the master. Frank (2 Replies)
Discussion started by: frankkahle
2 Replies

3. UNIX for Advanced & Expert Users

Moving NIS master to new machine

I am running a DNS/NIS server on and older 2.6 system. I would like to move it to a newer system running Sol9. I have not found a good HOWTO and was looking for some advice. Thanks in advance. Dave (4 Replies)
Discussion started by: dlalonde
4 Replies

4. Solaris

Problem while setting NIS master on Solaris 10

Hi All, I get below error while running cd /var/yp /usr/sbin/ypinit -m Error Code - 1 updated netmasks make : warning : target all not remade because of errors current working dir /var/yp *** error code 1 *** make : fatal error : command failed for target 'k' error running... (4 Replies)
Discussion started by: naw_deepak
4 Replies

5. Solaris

NIS master "ypwhich can't communicate with rpcbind"

Hello All, I just tried to create NIS master in my x86 vmware machine. I have followed the steps and created the necessary files and installed via ypinit command. Now the issue is after start the services when provide the ypwhich command showing following error. Please assist. bash-#svcs... (1 Reply)
Discussion started by: gowthamakanthan
1 Replies

6. HP-UX

NIS Master and Client problem

I have a NIS Master server and NIS Clients. But when I started the service all the process and files that should be owne by root apper by the owner 0 This is an example 0 1709 1708 0 10:06:10 ? 0:00 /usr/sbin/nfsd 4 0 1710 1709 0 10:06:10 ? 0:00 /usr/sbin/nfsd 4 0 1708 1 0 10:06:10 ? 0:00... (2 Replies)
Discussion started by: GCSG
2 Replies

7. Red Hat

Yppasswdd not running on nis master server

Goodmorning i am preparing Nis for my test lab.Running Redhat 5.4 on master and centos for my client.Master server running portmap,ypserv,yppasswdd and client running portmap,ypbind and ypxfrd. ypcat and other yp commands are running fine frm client.But when i try yppasswdd on client to change... (1 Reply)
Discussion started by: Vaibhav.T
1 Replies

8. UNIX Desktop Questions & Answers

How can I replicate master master and master master MySQL databse replication and HA?

I have an application desigend in PHP and MySQl running on apache web server that I is running on a Amazon EC2 server Centos. I want to implement the master-master and master slave replication and high availability disaster recovery on this application database. For this I have created two... (0 Replies)
Discussion started by: Palak Sharma
0 Replies

9. UNIX for Advanced & Expert Users

How to find out which server is LDAP/NIS master?

I have some scripts where I go and do some LDAP/NIS queries to report on users on Unix servers. What I am trying to figure out is, how do I know which server is the LDAP? The configs have been in place long before I took over so was hoping someone had some insight on how to figure this out. I must... (1 Reply)
Discussion started by: dagamier
1 Replies
nis_intro(7)						 Miscellaneous Information Manual					      nis_intro(7)

NAME
nis_intro - Network Information Service (NIS) introductory information DESCRIPTION
The Network Information Service (NIS) is a distributed name service that allows participating hosts to share access to a common set of sys- tem and network files. NIS allows the system administrator to manage these shared files on a single system. NIS is intended for use in a secure environment only, where gateways do not allow outside Internet access to the NIS protocol. NIS Maps Information distributed by NIS is stored in database files called maps. Most of the NIS maps represent files that were traditionally stored in the /etc directory. These files include the following: aliases group hosts netgroups networks passwd protocols rpc services In a secure environment, you can run NIS in a secure mode, thereby creating secure and nonsecure versions of the NIS maps. See the Secu- rity guide for more information. You can also use NIS to distribute files used by Automount or AutoFS, or to distribute other user-defined files. Each NIS map contains a set of keys and associated values. For example, as keys, the hosts map contains all host names on a network, and as values, the corresponding Internet addresses. Each NIS map has a map name, used by programs to access data in the map. NIS Domains A named set of NIS maps is called a domain. A system's "domain name" or "NIS domain" corresponds to the set of NIS maps that the system can access. You can think of an NIS domain as a set of systems that share the same set of NIS maps. A system's domain name is set at the time the system is booted by the /sbin/init.d/nis script using an entry in the /etc/rc.config.common file. System administrators can use the nissetup script to place entries in this file. The nissetup script is described in the Network Administration manual. You can determine your system's NIS domain using the domainname command. Refer to domainname(1). A domain name is required for retrieving data from an NIS database. NIS Client-Server Model NIS follows the client-server model of distributed services. There are two types of NIS servers - master and slave. The master server stores the master copy of the NIS maps for its domain; these are the only NIS maps that can be modified. Each domain has only one master server. Slave servers store copies of the master server's NIS maps. NIS slave servers can be spread throughout a network. Whenever an NIS map is updated on the master server, the master propagates the changes to each slave server in its domain. If the master is unavailable for any reason, the slave servers continue to make the NIS maps available to the NIS clients. Clients are all of the systems that can access NIS maps. When a client requires NIS information, it makes a remote procedure call (RPC) to one of the NIS servers to obtain the information. NIS Data Storage The data in NIS maps is stored as databases in dbm/ndbm, btree, or hash format. For example, the NIS map for the /etc/hosts file in the domain market might be stored in these dbm/ndbm files: /var/yp/mar- ket/hosts.byaddr.dir /var/yp/market/hosts.byaddr.pag /var/yp/market/hosts.byname.dir /var/yp/market/hosts.byname.pag The makedbm command takes an ASCII file such as /etc/hosts and converts it into dbm/ndbm files suitable for use by NIS. However, system administrators use the Makefile script in the /var/yp directory to create NIS map files and specify file format. The Makefile script then calls makedbm. Refer to the Network Administration manual for details on the Makefile script, specifying different formats, and other NIS management information. RELATED INFORMATION
Commands: domainname(1), svcsetup(8), ypbind(8), yppasswdd(8), ypserv(8), ypxfr(8) Files: svc.conf(4) Network Administration delim off nis_intro(7)
All times are GMT -4. The time now is 05:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy