Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
06-02-2002 06:46 PM
06-02-2002 06:46 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2002 07:16 PM
06-02-2002 07:16 PM
Re: NIS
If your using NIS, you need to mnake sure
that your have the correct /etc/nsswitch.conf
file in place. There are a few examples in
the /etc directory. Here are two of mine,
one being with NIS (/etc/nsswitch.conf) and
the other with no NIS. If you are using NIS the file will need to be moved.
# mv /etc/nsswitch.conf /etc/nsswitch.orig
# mv /etc/nsswitch.nis /etc/nsswitch.conf
HTH
~Michael
# /etc/nsswitch.nis:
#
# @(#)B.11.11_LR
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# uses NIS (YP) in conjunction with files.
#
passwd: files nis
group: files nis
hosts: nis [NOTFOUND=return] files
networks: nis [NOTFOUND=return] files
protocols: nis [NOTFOUND=return] files
rpc: nis [NOTFOUND=return] files
publickey: nis [NOTFOUND=return] files
netgroup: nis [NOTFOUND=return] files
automount: files nis
aliases: files nis
services: files nis
$ more /etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] dns [NOTFO
UND=return UNAVAIL=continue TRYAGAIN=return]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2002 07:20 PM
06-02-2002 07:20 PM
Re: NIS
One other thought, where exactly is the message being reported?
A user logging in ?
An 'ftp' session message?
In the /var/adm/syslog/syslog.log file?
Somewhere else....
Cheers
~Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2002 11:07 PM
06-02-2002 11:07 PM
Re: NIS
Check these files for invalid lines .
/etc/services
/etc/inetd.conf
compare the above files with
/usr/newconfig/etc/services
/usr/newconfig/etc/inetd.conf
you can copy those files from /usr/newconfig/etc to /etc/
#cp -p /usr/newconfig/etc/services /etc
#cp -p /usr/newconfig/etc/inetd.conf /etc
and give
#inetd -c
Now hope that error won't come again.
regards,
U.SivaKumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 03:31 AM
06-03-2002 03:31 AM
Re: NIS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 05:04 AM
06-03-2002 05:04 AM
Solutionas you have an issue with this services file check first if your services file does contain the service required , if not if there is a sign in there for the NIS compatibility (look at the man pages) and if so with ypcat you can look at the services file exported from the NIS server (check with YPWHICH what server that is) if the service required does exist in there , if it is so then you could have a issue with the NIS request itself (timing / no answer etc...)
I had a look at some known issues with NIS and there are some known timing issues which could case a slow reply from the NIS server to create this kind of problem , so it can be wise installing the latest NFS/NIS ONC megapatch and it's dependencies (they are important) about 15 patches are needed in total
If at the end it turns out to be a timing issue not fixed by patchuing then the nsswitch file can be usefull , putting up
services NIS [NOTFOUND=continue] files