SEO

#1 (**permalink**) 01-05-2008, 11:52 AM

Hi,

I am in an R&D lab developing applications that work along with HACMP
on AIX. I had recently created an install package using lppbuild.
After installing my package (*.bff file), which as far I know, should
only copy my compiled binary executables to their proper location on
the system, the HACMP cluster (version 5.3 and 5.4) can no longer
verify an synchronize.

Once I install my files, I get this error when I run Extended
Verification and Synchronization through SMIT:

--------------------------
cldare: Node blue1 is not running the same version of HACMP as
node blue2. DARE functionality is supported between nodes running
the same version of HACMP only.
---------------------------

where blue1 and blue2 are my two HACMP cluster nodes.

After I get this error, my cluster becomes completely hosed and
unrecoverable, even if I uninstall my package.

Any reason why this is happening? How would my install package have
an effect cause an HACMP version mismatch? I'm not even sure what the
error message is trying to say.

Cheers

#2 (**permalink**) 01-05-2008, 11:52 AM

On Aug 16, 12:13 am, bugbiteme <leon.p...@gmail.com> wrote:
> Hi,
>
> I am in an R&D lab developing applications that work along with HACMP
> on AIX. I had recently created an install package using lppbuild.
> After installing my package (*.bff file), which as far I know, should
> only copy my compiled binary executables to their proper location on
> the system, the HACMP cluster (version 5.3 and 5.4) can no longer
> verify an synchronize.
>
> Once I install my files, I get this error when I run Extended
> Verification and Synchronization through SMIT:
>
> --------------------------
> cldare: Node blue1 is not running the same version of HACMP as
> node blue2. DARE functionality is supported between nodes running
> the same version of HACMP only.
> ---------------------------
>
> where blue1 and blue2 are my two HACMP cluster nodes.
>
> After I get this error, my cluster becomes completely hosed and
> unrecoverable, even if I uninstall my package.
>
> Any reason why this is happening? How would my install package have
> an effect cause an HACMP version mismatch? I'm not even sure what the
> error message is trying to say.
>

My first guess is that your package changes the security settings of
system directories. Just check that your packages does not include any
directory entries like /usr /var ... and so on.

Of cource if you change some HACMP files ...
hth
Hajo

#3 (**permalink**) 01-05-2008, 11:52 AM

On Aug 16, 2:21 am, Hajo Ehlers <serv...@metamodul.com> wrote:
> On Aug 16, 12:13 am, bugbiteme <leon.p...@gmail.com> wrote:
>
>
>
> > Hi,
>
> > I am in an R&D lab developing applications that work along with HACMP
> > on AIX. I had recently created an install package using lppbuild.
> > After installing my package (*.bff file), which as far I know, should
> > only copy my compiled binary executables to their proper location on
> > the system, the HACMP cluster (version 5.3 and 5.4) can no longer
> > verify an synchronize.
>
> > Once I install my files, I get this error when I run Extended
> > Verification and Synchronization through SMIT:
>
> > --------------------------
> > cldare: Node blue1 is not running the same version of HACMP as
> > node blue2. DARE functionality is supported between nodes running
> > the same version of HACMP only.
> > ---------------------------
>
> > where blue1 and blue2 are my two HACMP cluster nodes.
>
> > After I get this error, my cluster becomes completely hosed and
> > unrecoverable, even if I uninstall my package.
>
> > Any reason why this is happening? How would my install package have
> > an effect cause an HACMP version mismatch? I'm not even sure what the
> > error message is trying to say.
>
> My first guess is that your package changes the security settings of
> system directories. Just check that your packages does not include any
> directory entries like /usr /var ... and so on.
>
> Of cource if you change some HACMP files ...
> hth
> Hajo

Wow. I've been scratching my head on this for a while now. You were
correct. I inadvertently changed the permissions on the /opt /etc and /
var directories in my installation package. Once I manually changed
them back (chmod 755) my cluster works again.

Now I need to track down the error in my installation package, but at
least I now know what is causing this problem to occur....and knowing
is half the battle!

Thanks!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

HACMP Extended Verification and Synchronization error