NIS+ breaks inetd, Solaris2.2/LX/DNS

NIS+ breaks inetd, Solaris2.2/LX/DNS

Post by Dae K » Thu, 23 Sep 1993 08:48:35



Hi,

I am setting up an LX running Solaris2.2 to be an NIS+ master
server. When I am done with root domain configuration, I rebooted
the machine to be sure things are ok and got the following messages
from inted during boot.

        Sep 21 17:41:05 inetd[308]: rquotad/rpc/udp: unknown service
        Sep 21 17:41:05 inetd[308]: rquotad/rpc/ticlts: unknown service
        Sep 21 17:41:05 inetd[308]: rusersd/rpc/udp: unknown service
        Sep 21 17:41:05 inetd[308]: rusersd/rpc/ticlts: unknown service
        Sep 21 17:41:05 inetd[308]: sprayd/rpc/udp: unknown service
        Sep 21 17:41:05 inetd[308]: sprayd/rpc/ticlts: unknown service
        Sep 21 17:41:05 inetd[308]: walld/rpc/udp: unknown service
        Sep 21 17:41:05 inetd[308]: walld/rpc/ticlts: unknown service
        Sep 21 17:41:05 inetd[308]: rstatd/rpc/udp: unknown service
        Sep 21 17:41:05 inetd[308]: rstatd/rpc/ticlts: unknown service

I consulted SunSolve and got some explanation (below). But it is not
harmless, as I found out. Some programs such as perfmeter are not
running as they are supposed to. Perfmeter displays RIP icon instead
of normal speedometer icon.

Would some one tell me what is causing this and how to fix?
FYI, the machine is also a DNS server which seems to work fine.

Thanks.

---------------------- SunSolve SRDB ID 2315 --------------------------

SRDB ID            : 2315

SYNOPSIS           :  "inetd unknown services" messages after nis reboot

DETAIL DESCRIPTION : These messages appear at boot on an NIS system
                     running >=4.1 when the NIS master is a system
                     running < 4.1.

SOLUTION SUMMARY   : The messages that appear are harmless.  They
                     report that some inetd services are unknown.  It
                     means that the NIS server does not know about
                     this service when booting.

                     Since the messages are harmless, no fix is needed.
                     But, two alternatives exist to eliminate the messages:

                     1) Upgrade NIS server to 4.1 and up, preferably
                        the most current release.

                     2) Comment out the unknown services in
                        /etc/inetd.conf on client.  Reboot client to
                        reflect changes. Reset file when NIS server
                        is running an OS > 4.1

SYMPTOMS           : At boot, the following messages appear:

        Feb 21 17:00:20 spear vmunix: swap on sd3b fstype spec size 29808K
        Feb 21 17:00:20 spear vmunix: dump on sd3b fstype spec size 29796K
        Feb 21 17:00:33 spear inetd[137]: uucp/tcp: unknown service
        Feb 21 17:00:35 spear inetd[137]: chargen/tcp: unknown service
        Feb 21 17:00:36 spear inetd[137]: chargen/udp: unknown service
        Feb 21 17:00:50 spear login: ROOT LOGIN console

KEYWORDS           : inetd services date chargen tcp udp boot

BUG REPORT ID      : 1033858

PRODUCT            : booting

SUNOS RELEASE      : All

HARDWARE RELEASE   : 4/40

 
 
 

NIS+ breaks inetd, Solaris2.2/LX/DNS

Post by Brett McC » Thu, 23 Sep 1993 14:18:57


   I am setting up an LX running Solaris2.2 to be an NIS+ master
   server. When I am done with root domain configuration, I rebooted
   the machine to be sure things are ok and got the following messages
   from inted during boot.

           Sep 21 17:41:05 inetd[308]: rquotad/rpc/udp: unknown service
           Sep 21 17:41:05 inetd[308]: rquotad/rpc/ticlts: unknown service
           Sep 21 17:41:05 inetd[308]: rusersd/rpc/udp: unknown service
           Sep 21 17:41:05 inetd[308]: rusersd/rpc/ticlts: unknown service
           Sep 21 17:41:05 inetd[308]: sprayd/rpc/udp: unknown service
           Sep 21 17:41:05 inetd[308]: sprayd/rpc/ticlts: unknown service
           Sep 21 17:41:05 inetd[308]: walld/rpc/udp: unknown service
           Sep 21 17:41:05 inetd[308]: walld/rpc/ticlts: unknown service
           Sep 21 17:41:05 inetd[308]: rstatd/rpc/udp: unknown service
           Sep 21 17:41:05 inetd[308]: rstatd/rpc/ticlts: unknown service

   I consulted SunSolve and got some explanation (below). But it is not
   harmless, as I found out. Some programs such as perfmeter are not
   running as they are supposed to. Perfmeter displays RIP icon instead
   of normal speedometer icon.

   Would some one tell me what is causing this and how to fix?
   FYI, the machine is also a DNS server which seems to work fine.

It means that you either need to edit your nsswitch.conf file to use
files before nisplus for services, or you need to fill the services
NIS+ table with the information inetd needs.

I prefer the second.  You can do this with:

        /usr/lib/nis/nisaddent services

Which will read your /etc/services file and fill the services.org_dir
table with the information.  You will probably want to do the same
to all of the standard NIS+ tables.  Type:

        /usr/lib/nis/nisaddent blah

For a list of all the tables that it knows about.

Brett McCoy
Computing and Network Services, Kansas State University
Manhattan KS  66506 / vox: (913) 532-4908  fax: (913) 532-5914

 
 
 

NIS+ breaks inetd, Solaris2.2/LX/DNS

Post by Wolfgang Ratzka t20 » Thu, 23 Sep 1993 19:59:52


  >     Sep 21 17:41:05 inetd[308]: rquotad/rpc/udp: unknown service
  >     Sep 21 17:41:05 inetd[308]: rquotad/rpc/ticlts: unknown service
  >     Sep 21 17:41:05 inetd[308]: rusersd/rpc/udp: unknown service
  >     Sep 21 17:41:05 inetd[308]: rusersd/rpc/ticlts: unknown service
  >     Sep 21 17:41:05 inetd[308]: sprayd/rpc/udp: unknown service
  >     Sep 21 17:41:05 inetd[308]: sprayd/rpc/ticlts: unknown service
  >     Sep 21 17:41:05 inetd[308]: walld/rpc/udp: unknown service
  >     Sep 21 17:41:05 inetd[308]: walld/rpc/ticlts: unknown service
  >     Sep 21 17:41:05 inetd[308]: rstatd/rpc/udp: unknown service
  >     Sep 21 17:41:05 inetd[308]: rstatd/rpc/ticlts: unknown service

  >It means that you either need to edit your nsswitch.conf file to use
  >files before nisplus for services, or you need to fill the services
  >NIS+ table with the information inetd needs.

No it means you have not filled the rpc NIS+ table, which is the
rpc-oriented counterpart to the services map.

--
     _
 |  | )

 
 
 

1. DNS search between Solaris2.5.1 and Solaris2.6

So have you tried to declare it as a null function ( { ; } ) in
your 2.6 source code and see if that makes a difference? Without
seeing anything pertinent I can't make very good guesses! But hey,
if you figure it out you could always enclose your work around in
an #IFDEF block where your test the was the OS version. I don't
recall the name of the define, but there is one and it is consitent.
Since the source code would have to be recompiled anyways - voila!

Jeff S. Dickson

2. PCI Vendor/Device IDs and Solaris

3. What breaks when NIS+ & DNS domain names are different

4. Xconfig timings help

5. nis(not nis+) on solaris2.1 and its setup.

6. CGI.pm: How to access the raw post data?

7. Does Solaris2.x runs on classics class (including IPX, LX,...) ?

8. Need help with Installation

9. NIS netgroup support broken under NIS+

10. audioplay broken on sun4m (lx, classic)?

11. Solaris2.6/inetd

12. DNS w/ NIS (NIS getting in the way?)

13. solaris2.3 inetd errors