Anyway to change the hostname after the install, we have had this thing
up for 3 months now and this is the first time it has done this.  The
only thing that has changed is the IP address but that was done about 3
weeks ago and we never had a problem until Tuesday of the current week.


Dustin D'Amour
Coyote Solutions Group
505.742.0066
www.coyotesolutions.com
 
"Relax...it's just an update for the patch to fix the nerf that nerfed
the fix for the update of the patch that broke the fix that was fixed."
--Unkown
 
"...Be not afraid of greatness: some are born great, some achieve
greatness, and some have greatness thrust upon them."  --William
Shakespeare

-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz at lucidpixels.com] 
Sent: Friday, September 08, 2006 9:16 AM
To: Dustin D'Amour
Cc: veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Strange Errors

Also, when I say just the hostname, I mean during the ICS installation.

On Fri, 8 Sep 2006, Dustin D'Amour wrote:

> We did install ICS before installing NB.  So just use the hostname and
> not the domain name (ie hostname.domainname.zzz) ?
>
> Dustin D'Amour
> Coyote Solutions Group
> 505.742.0066
> www.coyotesolutions.com
>
> "Relax...it's just an update for the patch to fix the nerf that nerfed
> the fix for the update of the patch that broke the fix that was
fixed."
> --Unkown
>
> "...Be not afraid of greatness: some are born great, some achieve
> greatness, and some have greatness thrust upon them."  --William
> Shakespeare
> -----Original Message-----
> From: Justin Piszcz [mailto:jpiszcz at lucidpixels.com]
> Sent: Friday, September 08, 2006 8:56 AM
> To: Dustin D'Amour
> Cc: veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] Strange Errors
>
> Yeah, you should install ICS before installing NB 6.0x and do not use
> FQDN
> hostnames, use the short hostname only.  Otherwise, you will have a
> whole
> sleuth of errors, like you are seeing.
>
> Justin.
>
> On Fri, 8 Sep 2006, Dustin D'Amour wrote:
>
>> I'm getting following errors:
>>
>>
>>
>> Activity Monitor failed and must be restarted.
>>
>> To recover, first correct the problem described below and then select
>> Refresh.
>>
>>
>>
>> Connection refused
>>
>>
>>
>>
>>
>> I've tried stopping and restarting services and no go still get same
>> error.  I don't understand why I'm all of the sudden getting the
>> Connection refused part of the error message.  Nothing has changed in
>> the last week that I can see that would cause this.  Also this
problem
>> is just not with the Activity monitor when I try to change the host
>> properties I get:
>>
>>
>>
>> Library Initialization failed.  Cobra communication error (195) (MM
>> Status 195)
>>
>>
>>
>> Sometimes I do not get that error and I'm able to open the host
>> properties up but then I do not get anything in the dialog when I try
>> clicking on one of the options such as Client Attributes or any of
the
>> other options.
>>
>>
>>
>>
>>
>> Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3
>>
>>
>>
>>
>>
>> Dustin D'Amour
>>
>> Coyote Solutions Group
>>
>> 505.742.0066
>>
>> www.coyotesolutions.com <http://www.coyotesolutions.com>
>>
>>
>>
>> "Relax...it's just an update for the patch to fix the nerf that
nerfed
>> the fix for the update of the patch that broke the fix that was
> fixed."
>> --Unkown
>>
>>
>>
>> "...Be not afraid of greatness: some are born great, some achieve
>> greatness, and some have greatness thrust upon them." --William
>> Shakespeare
>>
>>
>>
>>
>