It turns out that the "route add" statement in my /etc/rc.local was the
problem. I had changed the original /etc/rc.local to do proxy arp
route add default `/bin/hostname` 0
... one of those "F__d"
recommendations (don't want to tax the router too hard you know). My
local support guy - Brian Bunch of Sun Great Lakes, asked all the right
questions, and helped me diagnose the problem.
Going back to the generic route add statement and creating a
/etc/defaultrouter works fine.
Also recommended by "F__d" was to make the "127.0.0.1" line in the
/etc/hosts file be referred to as "localhost loopback loghost". Again,
Brian recommended changing back to the default of "loghost" referring to
the systems IP/hostname entry (e.g. 11.11.11.11 eve111 loghost)
Also, the reference in the "original question" to the DNS and BIND book
does work. Building an empty NIS hosts map
PS,
I need to use the code "F__d" in order to not offend anyone from the
"F__d" organization who might read this summary.
Regards,
Mark
mherberg@eve044.cpd.ford.com
"Opinions are my own, not my employers"
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Original Posting:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
System:
SS10 model 40 - GT
SunOS 4.1.3
Patches:
100103-11 100383-06 100844-02
100173-10 100448-01 100891-01
100185-01 100465-02 101192-01
100224-06 100482-04 100249-08
100507-04 100296-01 100513-02
100305-11 100623-03 100377-05
100726-10
Error Message at boot:
###########################################################################
.
.
.
NIS domainname .....
Starting NIS Services: ypserv ypbind ypupdated
Starting RPC keyservices
ifconfig ioctl (SIOCSIFBDRADDR): Invalid argument
flushing routing tables
(long delay)
yap093: bad value
^^^^^^^^^^^^^^^^^
.
.
yap093 login:
October 12 13:19:18 syslogd: line 33 unknown host loghost
October 12 13:18:31 automount 106: can't get my address
############################################################################
Question:
It appears that the system is not reading it's /etc/hosts table at boot..?..
The systems IP and hostname are in it's /etc/hosts table.
What would cause this?
I am trying to use a feature described in the O'Reilly "DNS and Bind" book, pg
119, on "Ignoring NIS". It recommends building an empty hosts NIS map, which along
with the magic cookie in /var/yp/Makefile will force the system to resolve names
in DNS.
The system boots fine when the NIS "hosts" map contains an entry for it, but when
I propagate an empty NIS "hosts" map, or even a map which does not contain this
host; and reboot, I get the error condition above.
Thank you for any feedback you can provide.
Regards,
Mark
mherberg@eve044.cpd.ford.com
+++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Thanks to all of the respondents. Here are their responses:
+++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Ah yes. The "manual" is incorrect in what it states about
the /etc/hosts file in relation to NIS.
The NIS hosts map REPLACES info in /etc/hosts, not adds
to it (like the + in /etc/passwd).
However, your local system needs at least its IP in /etc/hosts
so that rc.boot can configure the ethernet port. Once the
system fires up and runs ypbind, hosts info comes only from
the hosts map. We have tested this and it is true that
systems in only the /etc/hosts file and not in the NIS map
will not "exist" once the system binds.
So, you will need to update your server. No choice.
Oh, one more thing. If you want to "ignore" NIS, you
could just "not start it up".
If you do not have a /var/yp directory, the default
rc.local that comes with the system won't run ypbind.
Ciao for now,
Kevin Mah
+++++++++++++++++++++++++++++++++++++++++++++++++++++
it's not NIS that's the problem -- it's your
broadcast address setting. looks like your host
is either trying to set the wrong broadcast address
(what does your ifconfig line in /etc/rc.local ook like?)
or you have changed IP addresses between NIS and /etc/hosts:
make sure they are consistent!
--hal
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Well, I'm no DNS wiz, but I believe DNS isn't active either, until
somewhat later in the boot process. I'd be happy to discover I'm
wrong, but... that's the way most machines I've seen are set up.
You might try booting in single user, and running nslookup, or perhaps
doing an "echo eve044.cpd.ford.com | nslookup" somewhere near the
mount in your /etc/rc* files.
Dan Stromberg - OAC/DCS strombrg@uci.edu
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:26 CDT