Bottom line to fix was to admit defeat and reload the OS (I feel like a
Microsoft guy.) After the OS reload and hardware update for the nics, I
made certain to configure the ASE side first. Now the hostname matches.
Wendy Fong sent an idea that I did not consider and should have...
"Have you checked the TCR database (/usr/var/ase/config/asecdb)..."
... I think that would have been interesting. Seems like that should be
removed if you remove then reinstall trucluster which I also tried, but
maybe it sticks around.
Nikola Milutinovic and John Losey made some good suggestions about
general ip config which I am confident was done correctly initially,
and rechecked several times I might add, that's what makes it so frustrating.
As always, thanks for the help, original and Wendy's posts included.
Bryan
On Fri, 31 Mar 2000, Wendy Fong wrote:
> Date: Fri, 31 Mar 2000 16:40:42 -0800
> From: Wendy Fong <wfong_at_synacom.com>
> To: Bryan Rank <bryan_at_compgen.com>
> Subject: Re: hostname woes
>
> Have you checked the TCR database (/usr/var/ase/config/asecdb). I vaguely
> remembered the hostnames hide out in here also. We delete the database and
> recreate when we are having problems. (Do not do this on a production
> system unless it is down, you are really having problems and you know what
> you are doing!)
>
> wendy
>
>
> At 06:59 PM 3/31/00 -0500, you wrote:
> >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
>
> =====================
> Wendy Fong
> wfong_at_synacom.com
> 408.296.0303
>
> UNIX is very user friendly,
> it's just very particular about
> who it makes friends with.
> =====================
>
Received on Mon Apr 03 2000 - 14:14:39 NZST