VMware Communities: errorhandling? (Vim::login) ...

VMware

Up to Discussions in vSphere SDK for Perl

Sample Code
Tech Exchange

vSphere SDK for Perl:

This Question is Answered

2 "helpful" answers available (6 pts)

5 Replies Last post: Oct 16, 2009 12:46 AM by LarsOeschey

errorhandling? (Vim::login) posted: Oct 15, 2009 5:32 AM

LarsOeschey

9 posts since
Oct 9, 2009

Hi,

I'm trying to establish some errorhandling in my script to output to a logfile. Somehow I can't get this to work:

print LOG "login failed\n" if !(Vim::login(
service_url => $service_url,
user_name => $username,
password => $password));

in an error case I get the output on the console, but not in the logfile... How could that be done?

Lars

Re: errorhandling? (Vim::login)

1. Oct 15, 2009 6:57 AM

in response to: LarsOeschey

lamw

2,803 posts since
Nov 27, 2007

Without seeing more of your code, it's hard to say what is wrong ..

Take a look on how to output to a file using Perl: http://www.troubleshooters.com/codecorn/littperl/perlfile.htm

=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
VMware Code Central - Scripts/Sample code for Developers and Administrators
VMware Developer Comuunity
Twitter: @lamw

If you find this information useful, please award points for "correct" or "helpful".

Re: errorhandling? (Vim::login)

2. Oct 15, 2009 7:54 AM

in response to: lamw

LarsOeschey

9 posts since
Oct 9, 2009

There's not that much more code before

http://communities.vmware.com/images/emoticons/wink.gif

(btw, is there no [code] or quote tags here? Code gets really ugle when posted

use strict;
use warnings;
use VMware::VIRuntime;

my $log="vmbackup.log";
unlink $log;
open (LOG, ">".$log) or die "can't open log\n";
my $service_url="https://10.199.71.96/sdk";
my $username="vsadmin";
my $password="vadmin";
my $backup_variable="backup";
my $last_backup="last_backup";

print LOG "start!\n";
print LOG "login failed\n" if !(Vim::login(
service_url => $service_url,
user_name => $username,
password => $password));

The logfile itself works, the first print LOG statement works fine. It must be something with the way Vim::login returns...

Re: errorhandling? (Vim::login)

3. Oct 15, 2009 9:09 AM

in response to: LarsOeschey

lamw

2,803 posts since
Nov 27, 2007

Actually there are code and quote tags but you wrap them in "{" "}"

code tags

quote tags

Any reason you're not using the default Util::connect() and Util::disconnect() code that VMware already wrote in their perl modules?

You may want to take a look at this page http://www.vmware.com/support/developer/viperltoolkit/doc/perl_toolkit_guide.html to help you get started, much of the comand line parms and auth/connection code has been simply to help you get a script up and running much faster.

Re: errorhandling? (Vim::login)

4. Oct 15, 2009 2:04 PM

in response to: LarsOeschey

stumpr

451 posts since
Sep 26, 2007

You could use eval blocks:


eval {
     Vim::login( service_url=> $service_url, user_name => $username, password => $password);
};

if ($@) {
     # A fault was thrown
     print LOG $@ . "\n";

     # ...any other error handling...
}

You can also do string comparisons against the $@ variable to see if it matches a fault. For example, login could throw "InvalidLogin - Thrown if the user and password combination is invalid." You could use code like:


if ( $@ =~ m/InvalidLogin/gi ) {
      print LOG "Invalid Login ($@)\n";
}
else {
      print LOG "Login Error: ($@)\n";
}

This would let you handle specific faults if you wanted to recover or trigger another code path as a result.

Re: errorhandling? (Vim::login)

5. Oct 16, 2009 12:47 AM

in response to: lamw

LarsOeschey

9 posts since
Oct 9, 2009

{quote}Any reason you're not
using the default Util::connect() and Util::disconnect() code that
VMware already wrote in their perl modules?{/quote}

Edit: ok, my quote tags obviously are wrong Looks like the correct syntax is well hidden somewhere and not included in the Editor here...

I'm trying to not use commandline options, and I'm trying to do some logging, since the script will run unattended. The Vim::login just was in some sample script, but with this problem (methods not returning a string to the script), Util::connect() wouldn't make much difference I think...

Go to original post