[Linux-cluster] help reqd. - VMware ESX 3.5 fencing

Thu Feb 28 15:32:28 UTC 2008

We should note in the script the differences, and dependencies, and
which ESX server it runs on correctly, so others don't run down the same
path.

Regards,
-C

PS thanks, and good to know this - upgrading might have a whole lot
scarier.

On Thu, 2008-02-28 at 09:06 -0600, Brian Kroth wrote:
> I'm running Gentoo, but that shouldn't make a difference.  Here's what I
> did:
> 
> - install various support perl packages as listed in the VMWare perl
>   tooklit 1.5 source install instructions.  This is the one from ESX
>   3.5.
> 
> - install VMware-VIPerl-Toolkit-1.5.0-source.tar.gz
> 
> - copy the AppUtil directory as listed in the source code
> 
> - run the test cmd I posted earlier "echo stuff | fence_vi3"
> 
> I think the disconnect is probably due to differing vipertoolkit
> versions.
> 
> I had also tried switching VIM2Runtime.pm with VIM25Runtime.pm, but to
> no avail.  Switching that line to VIRuntime is what did it.
> 
> Brian
> 
> chris barry <Christopher.Barry at qlogic.com> 2008-02-28 09:51:
> > 
> > I'm running RHEL4u5 VMs and VI3.02, and I did not encounter this error.
> > What versions are you using? VI3.5, and what VM distro?
> > 
> > Ok, what I am getting at is what made you have to change that line!
> > 
> > ;)
> > 
> > On Thu, 2008-02-28 at 19:47 +0530, Panigrahi, Santosh Kumar wrote:
> > > No Chrish, I have copied Apputil directory from viperltoolkit directory
> > > (/tmp/viperltoolkit/apps) to my site perl directory
> > > (/usr/lib/perl5/site_perl/5.8.8) as per your suggestion. But after that
> > > on running your fencing script, I got the same error, as reported by
> > > Brian. Then I changed the package to VMware::VIruntime at line 45 and
> > > the script worked fine without giving any compilation problem.
> > > 
> > > I don't know how u got the impression from the below mail chain that we
> > > have executed the script successfully without coping the Apputil
> > > directory to site_perl directory. 
> > > 
> > > Thanks and Regard,
> > > Santosh
> > > 
> > >  
> > > -----Original Message-----
> > > From: linux-cluster-bounces at redhat.com
> > > [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Christopher Barry
> > > Sent: Thursday, February 28, 2008 7:20 PM
> > > To: linux clustering
> > > Subject: RE: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > > 
> > > 
> > > What version of redhat are you using?
> > > 
> > > Are you saying that instead of copying the AppUtil directory
> > > post-install of the viperltoolkit, you simply changed the use line to
> > > use VMware::VIRuntime;?
> > > 
> > > Regards,
> > > -C
> > > 
> > > -----Original Message-----
> > > From: linux-cluster-bounces at redhat.com on behalf of Brian Kroth
> > > Sent: Thu 2/28/2008 8:29 AM
> > > To: Panigrahi, Santosh Kumar
> > > Cc: linux clustering
> > > Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > >  
> > > That was it.  
> > > 
> > > Thanks,
> > > Brian
> > > 
> > > Panigrahi, Santosh Kumar <Santosh.Panigrahi at in.unisys.com> 2008-02-28
> > > 09:37:
> > > >    Hello Brian,
> > > > 
> > > >    I had also faced the same problem. Just change the line no 45 in
> > > your
> > > >    script. The original line is <use VMware::VIM2Runtime>. Make it to
> > > > 
> > > >    <use VMware::VIRuntime;> After changing this it worked fine for me
> > > and
> > > >    hopes it will also solve your compilation aborted problem.
> > > > 
> > > >    Chris,
> > > > 
> > > >    Thanks for giving your precious time on debugging the problem,
> > > which I
> > > >    had reported without coping the Apputil directory.
> > > > 
> > > >    Thanks and Regards,
> > > > 
> > > >    Santosh
> > > > 
> > > >    -----Original Message-----
> > > >    From: linux-cluster-bounces at redhat.com
> > > >    [[1]mailto:linux-cluster-bounces at redhat.com] On Behalf Of Brian
> > > Kroth
> > > >    Sent: Thursday, February 28, 2008 4:15 AM
> > > >    To: chris barry
> > > >    Cc: linux clustering
> > > >    Subject: Re: [Linux-cluster] help reqd. - VMware ESX 3.5 fencing
> > > > 
> > > >    More perl questions:
> > > > 
> > > >    $ echo -e
> > > >
> > > "server=vmware\nvmname=gfstest3\nusername=fencer\npassword=fencerpw\nop
> > > >    eration=reset" | /sbin/fence_vi3
> > > > 
> > > >    The component 'privilegeList' has already been installed in class
> > > >    -->AuthorizationManager<-- as a HASH(0x1f779834)
> > > > 
> > > >      (this time a scalar)
> > > > 
> > > >     at
> > > /usr/lib/perl5/vendor_perl/5.8.8/i686-linux/Class/MethodMaker.pm
> > > >    line 20
> > > > 
> > > >    BEGIN failed--compilation aborted at
> > > >    /usr/lib/perl5/site_perl/5.8.8/VMware/VIM25Runtime.pm line 17, <>
> > > line
> > > >    6.
> > > > 
> > > >    Compilation failed in require at (eval 27) line 3, <> line 6.
> > > > 
> > > >    Any thoughts?
> > > > 
> > > >    Thanks,
> > > > 
> > > >    Brian
> > > > 
> > > >    chris barry <Christopher.Barry at qlogic.com> 2008-02-26 17:30:
> > > > 
> > > >    > Read the top section of the script itself. I explain that the
> > > install
> > > > 
> > > >    > script of viperltoolkit does not install the AppUtil directory
> > > with
> > > >    the
> > > > 
> > > >    > rest of itself in your particular site_perl dir.
> > > > 
> > > >    >
> > > > 
> > > >    > do a
> > > > 
> > > >    > $ locate site_perl
> > > > 
> > > >    > to see where on your system has your site_perl director(y|ies),
> > > and
> > > >    look
> > > > 
> > > >    > in each one to find the other vmware module dirs (includes)
> > > listed in
> > > > 
> > > >    > the top of the script. Then copy the AppUtil dir (from the
> > > >    viperltoolkit
> > > > 
> > > >    > source) into the same site_perl as the rest, and at the same
> > > level.
> > > > 
> > > >    >
> > > > 
> > > >    > e.g.
> > > > 
> > > >    > ...site_perl
> > > > 
> > > >    >        |-AppUtil
> > > > 
> > > >    >        |-VMware
> > > > 
> > > >    >        `-other stuff
> > > > 
> > > >    >
> > > > 
> > > >    >
> > > > 
> > > >    > Once the AppUtil dir is present in the right location, it should
> > > work
> > > > 
> > > >    > ok. I had to figure this out the hard way. ;)
> > > > 
> > > >    >
> > > > 
> > > >    >
> > > > 
> > > >    > Good Luck,
> > > > 
> > > >    > -C
> > > > 
> > > > References
> > > > 
> > > >    1. mailto:linux-cluster-bounces at redhat.com
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --
> > > Linux-cluster mailing list
> > > Linux-cluster at redhat.com
> > > https://www.redhat.com/mailman/listinfo/linux-cluster
> > 
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-cluster