HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problem with NIS maps
Operating System - HP-UX
1825737
Members
2474
Online
109687
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2007 06:40 AM
07-06-2007 06:40 AM
Problem with NIS maps
Hi there --
I am trying through SAM to transfer all maps from the Master NIS to the Slave NIS server. When I checked the ypxfer.log file, I noticed the following entries:
Fri Jul 6 14:34:15: ypxfr: transferred map auto.master from cosmos1 (2 entries)
Fri Jul 6 14:34:15: ypxfr: can't get master of bootparams
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of ethers
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of group
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of hosts
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of mail
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: transferred map netgroup from cosmos1 (2 entries)
Fri Jul 6 14:34:16: ypxfr: can't get master of netid
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of netmasks
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of networks
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of passwd
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of protocols
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of publickey
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of rpc
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of services
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: transferred map ypservers from cosmos1 (2 entries)
I checked the Master and NIS server, and the files in question do exist. How can I correct this? Thanks.
I am trying through SAM to transfer all maps from the Master NIS to the Slave NIS server. When I checked the ypxfer.log file, I noticed the following entries:
Fri Jul 6 14:34:15: ypxfr: transferred map auto.master from cosmos1 (2 entries)
Fri Jul 6 14:34:15: ypxfr: can't get master of bootparams
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of ethers
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of group
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of hosts
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of mail
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: transferred map netgroup from cosmos1 (2 entries)
Fri Jul 6 14:34:16: ypxfr: can't get master of netid
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of netmasks
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of networks
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of passwd
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of protocols
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of publickey
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of rpc
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: can't get master of services
reason: no such map in server's NIS domain
Fri Jul 6 14:34:16: ypxfr: transferred map ypservers from cosmos1 (2 entries)
I checked the Master and NIS server, and the files in question do exist. How can I correct this? Thanks.
A Journey In The Quest Of Knowledge
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2007 06:46 AM
07-06-2007 06:46 AM
Re: Problem with NIS maps
check on the client side to check if it is pointing to the right NIS server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2007 07:26 AM
07-06-2007 07:26 AM
Re: Problem with NIS maps
Hi there --
I ran the ypwhich command on the slave server and compared it to that on the master. The slave outputted the FQDN, while that on the master generated the hostname.
I modified the /etc/hosts file on the slave to match that on the master, and restarted the nis.server and nis.client scripts. When I tried to do the same procedure, the output was the same as before.
I ran the ypwhich command on the slave server and compared it to that on the master. The slave outputted the FQDN, while that on the master generated the hostname.
I modified the /etc/hosts file on the slave to match that on the master, and restarted the nis.server and nis.client scripts. When I tried to do the same procedure, the output was the same as before.
A Journey In The Quest Of Knowledge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2007 03:44 PM
07-06-2007 03:44 PM
Re: Problem with NIS maps
> I am trying through SAM to transfer all
> maps from the Master NIS to the Slave NIS
> server. [...]
Perhaps I'm just dense, but that doesn't tell
me either what you did, or where you did it.
Knowing how this stuff was initially
configured, and whether it ever worked, might
be valuable.
If I were to offer a cash payment, would
there be any better chance of seeing the
output from a "ypwhich -m" command anywhere?
There's much to be said for running ypinit
(with the appropriate options) manually on
all the NIS servers. ("man ypinit")
> maps from the Master NIS to the Slave NIS
> server. [...]
Perhaps I'm just dense, but that doesn't tell
me either what you did, or where you did it.
Knowing how this stuff was initially
configured, and whether it ever worked, might
be valuable.
If I were to offer a cash payment, would
there be any better chance of seeing the
output from a "ypwhich -m" command anywhere?
There's much to be said for running ypinit
(with the appropriate options) manually on
all the NIS servers. ("man ypinit")
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP