Hi,
I have a good one for you guys.
In the past I have had problems with TRUCluster installations on NETDEV_1
(in /etc/rc.config) or greater acting strangely, so as a rule I have
vowed that all clusters that I configure will use NETDEV_0. Today I have
run across something interesting
If you load Tru64 and configure tu1 (or ee1 in my case), THEN you configure
tu0 (or ee0 in my case). It seems like the hostname is somehow bound
to ee1. Even though I provided the name dcs1-ee1 when using netconfig.
My /etc/hosts file was as follows...
127.0.0.1 localhost
158.155.4.219 dcs1 dcs1-ee1 #HOSTNAME something or other comment here
192.168.3.11 dcs1-ee0 dcs1-ee0
I changed it to the following ....
127.0.0.1 localhost
192.168.3.11 dcs1 dcs1-ee0
158.155.4.219 dcs1-ee1 dcs1-ee1
Now when I install the Trucluster package using setld and it asks for
my IP Name, it gives me the default of "dcs1" (that's my hostname).
When I hit return it complains that I have interface defined for it.
Heres the kicker. If I edit the /etc/hosts file and take out the name
dcs1-ee0, I can still use it for the config, even though it's not in
hosts or rc.config!
I looked for secret files in /tmp, and found some, but they were all as
was in my hosts file. I then found the secret directory /usr/.smb. that
has lots of TCR this and TCR that scripts and context files for the
install in it, but nothing that would hose up hostname. I am frustrated as
I have seen this before and it has beaten me. This is the second time.
Does anyone know how/why hostname is being bound in this way?
Thanks,
Bryan Rank
Received on Sat Apr 01 2000 - 00:00:06 NZST