nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

email-admin.ipl

dkuntze

Does anyone have any experience with the email-admin.ipl on windows w/OD 6.5?

I have modified the script to parse the resulting log file by hardcoding it into the script, but this is not the ideal config. In its original state, the script read the log data from stdin. How can I pass the log data in stdin from my deployment script? I saw a older post using OD 5 that had a dnrProperties element, that doesn't seem to exist in od 6.5. ,that probably would have fixed this problem.

Thx!

Find more posts tagged with

Comments

Adam Stoller

OD will send it's own internal log information, in XML format, through STDIN to the DNR script - all you need to do is process the input stream.
To try to make that easier, OD ships with a module (IWXML.pm) in the ODHOME/solutions/perl directory (you can either reference it from there, or copy it to somewhere else that you prefer).

Read the perldoc on IWXML.pm for more information about its usage.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dkuntze

It doesn't appear to be working for me.

I've changed the dnrProperties in odbase to:

<dnrProperties allowDnrExecution="yes"
infoStreamFormat="log" />

Does not work. Here's my deployment bit:

<deployment transactional="yes" >
<dnrDeploymentJob location="source" when="after" state="always">
<script cmd="C:\IW-Home\OpenDeployNG\conf\mail-admin.ipl -t dkuntze@fnni.com -s 001fntces04.fnb.fnni.com" async="no" where="C:\IW-Home\OpenDeployNG\conf" />
</dnrDeploymentJob>
<execDeploymentTask useDefinition="test_deployment" />
</deployment>

It just hangs when it tries to load the in memory log file.

I CAN get it to send an email if I hard code the path in the script and invoke it from the command line.

Adam Stoller

Ah - I think the problem is that you are using dnrDeploymentJob - which may be right in terms of when you want the script to run - but which I seem to recall is either running too-early or too-late to get the in-memory log. You might be able to use a dnrDeployment [no Job] with a triggerPoint of something like before disconnect (I don't remember the trigger points off the top of my head) and be able to get it to work that way.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dkuntze

I converted the deployment file to this:

<deployment transactional="yes" >
<execDeploymentTask useDefinition="test_deployment">
<deployNRun>
<dnrDeployment location="source" when="after" state="always" triggerPoint="disconnect">
<script cmd="C:\IW-Home\OpenDeployNG\conf\mail-admin.ipl -t dkuntze@fnni.com -s 001fntces04.fnb.fnni.com" async="no" where="C:\IW-Home\OpenDeployNG\conf" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
</deployment>

I'm not sure the script is even executing...

Johnny

On Windows you need to spoon feed the PERL command.

C:\IW-Home\iw-perl\perl.exe C:\IW-Home\OpenDeployNG\conf\mail-admin.ipl

or where your teamsite perl installation is (I'm guessing from the .ipl extension)

Try that.

John Cuiuli

dkuntze

Wow... something must be really screwed up.

Still doing the same behavior... appears to execute... but does not.

I added a logging line to the script that would tell me if it was firing or not. It is not. Command line still works though.

here's the interesting bits from the deployment log:

ENG: 2005-01-31 13:44:29 CST GMT-06:00 Thread-44 After CLEANUP, res=1
ENG: 2005-01-31 13:44:29 CST GMT-06:00 Thread-44 exiting cleanup
ENG: 2005-01-31 13:44:29 CST GMT-06:00 Thread-44 entering task-done
ENG: 2005-01-31 13:44:29 CST GMT-06:00 Thread-44 still waiting for 0
LIB: 2005-01-31 13:44:29 LOGFILE=[C:\IW-Home\OpenDeployNG\log\darins_deployments\src.deploy_test_2.test_deployment.001teamsite01.to.intranet_d02.log]
LIB: 2005-01-31 13:44:29 Locale=[English_UnitedStates.MS1252@Binary]
LIB: (2) 2005-01-31 13:44:29 Executed script [C:\IW-Home\iw-perl\iwperl.exe C:\IW-Home\OpenDeployNG\conf\mail-admin.ipl -t dkuntze@fnni.com -s 001fntces04.fnb.fnni.com] where [C:/IW-Home/OpenDeployNG/conf] as [] succeeded
ENG: 2005-01-31 13:44:29 CST GMT-06:00 Thread-44 PostDisConnect Dnr still waiting for 0
ENG: 2005-01-31 13:44:29 CST GMT-06:00 Thread-44 Deleting the internal config file = C:\IW-Home\OpenDeployNG\log\.deploy_test_2.test_deployment.intranet_d02
ENG: 2005-01-31 13:45:12 CST GMT-06:00 Published leg event depUuid=[75000170-73c0-11d9-83de-bd76a586b29d] legLabel=[intranet_d02.test_deployment] nextUuid=[null] nextDep=[null]
ENG: 2005-01-31 13:45:12 CST GMT-06:00 Thread-44 Job ID=m12 Deployment leg=intranet_d02.test_deployment Elapsed Time=18125 ms <<<
ENG: 2005-01-31 13:45:12 CST GMT-06:00 Thread-44 End logfile [C:\IW-Home\OpenDeployNG\log\darins_deployments\src.deploy_test_2.test_deployment.001teamsite01.to.intranet_d02.log]

Adam Stoller

You may need to add a bunch of different debugging lines to the script to see what's happening - don't forget to verify that the script itself compiles (iwperl -w -c scriptname) because I don't believe OD will treat failure to run the DNR script as a failure of the DNR (it didn't used to anyway, perhaps it's been fixed?)

If you're still having trouble with it - please post the script.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dkuntze

It appears that the script is fine:

C:\IW-Home\OpenDeployNG\conf>iwperl -w -c mail-admin.ipl
mail-admin.ipl syntax OK

The problem is, as it would seem, the script is never getting invoked. The OD logs show it as being executed, but it really never fires as far as I can tell. I have added a line that creates a line in a text file if it executes. Executing it manually from a command line, manually, the script fires correctly. This is the part that I don't get....

Adam Stoller

Let me try this again ... if you're having trouble debugging this - please post the script.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dkuntze

as I stated before, I don't think its even executing... but here you go:

#!/usr/local/bin/perl -w
######################################################################
# Copyright 2002,2004 Interwoven, Inc.
# All Rights Reserved.
######################################################################

=head1 Script: mail-admin

Send email to the "Administrator", reporting on successfully
and unsuccessfully deployed files.

NOTE: designed for use with OpenDeploy 6.0

NOTE: this script requires iwperl

=head1 Usage

Usage: mail-admin.ipl -h | -v | -t to-address -s mail-server

-h - print this information
-v - print version information
-t to-address - email address to send message
-s mail-server - mail server hostname (e.g., smtp.company.com)

=cut

use Mail: Smiley Frustrated

endmail;
use Getopt: Smiley Frustrated

td;
use vars qw($opt_h $opt_v $opt_t $opt_s);

my $VERSION = "6.0.0_01";

open(DAT,">>mail-admin.log") || die("Cannot Open File");
print DAT "$VERSION";
close(DAT);

my $IWOD60HOME = "";
if ($^O eq "MSWin32"){
$IWOD60HOME = $ENV{IWOD60HOME};
}
else {
if (open(IN, "</etc/defaultiwod60home")){
$IWOD60HOME = <IN>;
$IWOD60HOME =~ s/\s*$//g;
close(IN);
}
}
mydie("Unable to determine location of IWOD60HOME") if ($IWOD60HOME eq "");

showUsage() if (!getopts("hvt:s:"));
showVersion() if ($opt_v);
showUsage() if ($opt_h || !$opt_t);

eval('@INC = (@INC, "$IWOD60HOME/solutions/perl");require IWXML;');
#=====================================================================
my $subject = "OpenDeploy: ";
my $message = "";
my $xml_obj = IWXML::GetLogDataFromSTDIN();
my @f_pass = $xml_obj->GetSucceededFiles();
my @f_fail = $xml_obj->GetFailedFiles();
my @f_gone = $xml_obj->GetSucceededDeletedFiles();

my $counts = "(" . scalar(@f_fail) . "/" . scalar(@f_pass) . "/" .
scalar(@f_gone) . ")";

if (@f_fail){
$subject .= "Failed $counts";
$message .= "Failed to deploy:\n" . "=" x 70 . "\n";
foreach(@f_fail){
$message .= "$_\n";
}
$message .= "\n";
}
else {
$subject .= "Success $counts";
}

$message .= "Successfully deployed:\n" . "=" x 70 . "\n";
foreach(@f_pass){
$message .= "$_\n";
}
$message .= "\n";

if (@f_gone){
$message .= "Successfully deleted:\n" . "=" x 70 . "\n";
foreach(@f_gone){
$message .= "$_\n";
}
$message .= "\n";
}

#=====================================================================
my %mail = (Smtp => "$opt_s",
To => "$opt_t",
From => "OpenDeploy\@$opt_s",
Subject => "$subject",
Message => "$message");
sendmail(%mail) || doErrorExit(-2);
doErrorExit(0);

#=====================================================================
# showVersion
# Shows the version number of this script and exits with a non-zero
# status.
#=====================================================================
sub showVersion{
mydie("$0 v. $VERSION\n");
}

#=====================================================================
# showUsage
# Runs perldoc on the [calling] script to extract the usage information
# No return value, exits with a non-zero status.
#=====================================================================
sub showUsage{
(my $perlpath = $^X) =~ tr|\\|/|;
$perlpath =~ s|(.*)/.+|$1|;
my $scriptname = $0;
$scriptname =~ s|(.*)/(.+)|$2|;
system "$perlpath/perldoc $scriptname";
doErrorExit(-2);
}

#=====================================================================
# mydie
# dump message onto STDERR and then exit in such a way that OpenDeploy
# will regard it as a failure to run.
#=====================================================================
sub mydie{
my $msg = $_[0];
warn($msg);
doErrorExit(-2);
}

#=====================================================================
# doErrorExit
# send the appropriate error code to
# OpenDeploy (formatted in XML) and exit
#=====================================================================
sub doErrorExit {
my $retval = shift;
# currently, the next two lines get lost
# would be nice to be able to capture the output
# in the actual deployment logs
printf STDERR "<response result='error: %s'/>\n", $Mail: Smiley Frustrated

endmail::error;
printf STDERR "<response result='log: %s'/>\n", $Mail: Smiley Frustrated

endmail::log;
printf ("<response code=\"%d\"/>\n", $retval);
exit($retval);
}

Adam Stoller

You say its not executing.
You say you added debugging.
I can't tell what you did for debugging unless you show the script.
Now that you showed the script - I'd suggest making the following changes:

Adjust the mydie routine to use the same log file:sub mydie{
my $msg = $_[0];
if (open(DAT, ">>c:/temp/mail-admin.log")){
print DAT "$msg\n";
close(DAT);
}
warn($msg);
doErrorExit(-2);
}

With those two changes in place - try running it again via OD and see if the output file gets created.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dkuntze

I rewrote the script as you dictated and I still did not get an output file.

This is what is leading me to the "the script is not firing" statement.

Here is the interesting bit from the log:
LIB: (2) 2005-02-02 16:01:28 Executed script [C:\IW-Home\iw-perl\iwperl.exe C:\IW-Home\OpenDeployNG\conf\mail-admin.ipl -t dkuntze@fnni.com -s 001fntces04.fnb.fnni.com] where [C:/IW-Home/OpenDeployNG/conf] as [] succeeded

Looks like its executing... but I don't see anything happening. Is there a error log somewhere that might provide some helpful info?

Thanks!!

Adam Stoller

Try making the following change in your deployment config file - and see if that fixes things:


C:\IW-Home\iw-perl\bin\iwperl.exe C:\IW-Home\OpenDeployNG\conf\mail-admin.ipl -t dkuntze@fnni.com -s 001fntces04.fnb.fnni.com

If so - you should file a feature request / bug with Support to indicate that if OD is unable to execute a program (in this case it should be getting a file-not-found error somewhere) - then it should at least log something (and potentially abort the deployment?)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dkuntze

Thanks Fish! That did the trick.

For reference, I also figured out the right combo for the execution using the DNR to grab the deployed files from STDIN:

<dnrDeployment location="source" when="after" state="always" triggerPoint="transfer">
<script...>
</dnrDeployment>

Johnny

woops.. that looks like a typo on my behalf.

Sorry, but at least I had the general idea!

John Cuiuli

Migrateduser

excellent thread guys, was able to get this working without a hitch during my upgrade process. thanks!

-------------------
World of Warcraft  Illidan/Horde