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; } } }

iwsend_mail works only from command line

JackIntheBox

My send mail script is not working from the workflow, but with the required parameters triggers successfully from the command line. I have posted the script here, and if someone can spot anything wrong, or has encountered this problem before, please do reply.

Also, the same script is functioning very well in our production environment. I am thinking it might be because of some changes in the environment variables, since we installed MetaTagger on the development server a couple of days ago. The email problems began immediately thereafter, though I am not a 100% sure that this is a cause and effect situation.

The workflow calls the script though the following command:

<command v="/opt/iw-home/custom/bin/iwsend_mail.ipl __TAG__('iw_product_group_author'); Super_Author"/>
The output of the jobspec file is normal too. Can anyone throw some light on this situation.

We are on 5.5.2 SP3 and Solaris, OD 5.6, DD 5.6 SP1 and MT3.5.

Thanks!!

Edited by JackIntheBox on 06/11/03 09:47 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

First, I'd suggest you get a more recent copy of iwsend_mail.ipl to base your custom script on, and then I'd suggest you do, in fact, make it a copy (in another location and/or with a different name) so that you aren't modifying product deliverables.

It's unclear where exactly the problem is occurring - so I'd then recommend (if the problem persists after taking care of the above), liberally sprinkling debug code in the script so that when it gets run by workflow you can look at some log file and see what information it got, where it went, and where it stopped.

Once you have that information - if you cannot figure out how to fix it - post the information with the new version of the script, and someone here will probably be able to assist you - but hopefully, having gone through the above you'll be able to figure out how to fix it yourself.

--fish
(Interwoven Senior Technical Consultant)

JackIntheBox

fish:
I did as you said, I now have the new version of iwsend_mail, and again I have the same problem. The email works from the command line, but doesnt work from the workflow. I have attached the new script I am using.

Output from logs:
iwtrace.log:
[Wed Jun 11 19:01:19 2003] Unable to initialize arena: Arena is not active
[Wed Jun 11 19:03:36 2003] Unable to initialize arena: Arena is not active
[Wed Jun 11 19:04:36 2003] Unable to initialize arena: Arena is not active
[Wed Jun 11 19:05:36 2003] Unable to initialize arena: Arena is not active
from iwjoberrors.log:
[Wed Jun 11 19:04:36 2003] Could not run /opt/iw-home/custom/bin/iwsend_mail.ipl tfsuser Business_Unit_Review for task 5356; retrying in 1 minute
[Wed Jun 11 19:05:36 2003] Could not run /opt/iw-home/custom/bin/iwsend_mail.ipl tfsuser Business_Unit_Review for task 5356; retrying in 1 minute

No other logs were generated.
Thanks

Adam Stoller

I must assume that code lines 53 and 54:

my $maildomain="xxxxx.com";
my $mailserver="xxxxxxx.com";

are using ****'s only for this posting - yes? Have you verified that the $mailserver is actually an SMTP server that you can connect to from your TeamSite server?
I'll also have to assume that code line 56:

my $email_mapping_file="/opt/iw-home/custom/cfg/email_map.cfg";

represents a configuration file in the appropriate format for iwsend_mail.ipl
From line 57:

my $debug_output="/tmp/iwsend_mail.log";

did anything ever show up in this log? I'm guessing that it didn't because of a typo on line 95:

             'do' => my $debug_output,

(remove the my).

Having gone through all that - you previously indicated that you were passing in certain arguments on the command line from the wft:

<command v="/opt/iw-home/custom/bin/iwsend_mail.ipl __TAG__('iw_product_group_author'); Super_Author"/>

Presumably the tag iw_product_group_author is a userid, which from line 105-107 should get stored as an initial To address:

if (defined($ARGV[0]) && $ARGV[0] !~ /^\d+$/){
    push(@{$opts{t}}, shift);
}

However, the second argument "Super_Author" is almost definitely getting misinterpreted on line 121:

my($wfid, $taskid, $area) = (@ARGV[0..2]);

as being a workflow id, then the actual workflow id is getting stored in $taskid, and the actual taskid will be getting stored in $area and at this point I think all hope is lost.
I'd suggest making sure you understand the code before you try to change it to do something else.

--fish
(Interwoven Senior Technical Consultant)

JackIntheBox

Yes, the xxxxx's are for the posting.
The mailserver is a valid SMTP server since I am able to send emails from the command line, and the task transitions successfully.
Yes the configuration file exists, and translates usernames correctly since I am able to run from the command line.
I have corrected the typo (thanks for that!!) for the log file, but there was no logfile created.

I used this to run from the command line again:
/opt/iw-home/custom/bin/iwsend_mail.ipl kattap 5651 5656 /default/main/tf.com/WORKAREA/kattap2

The relevant code from the jobspec file is:
<command v='/opt/iw-home/custom/bin/iwsend_mail.ipl kattap'/>

I am not using the command I specified in the earlier email since I wanted to hardcode the recepient's name and also there is no need to specify the succesor task in the new version of sendmail.
I really appreciate all your help and thanks again for your quick response.

2up.png

Adam Stoller

Is it still not working?
Based on what you indicated - (getting rid of the second preliminary argument and fixing the one typo I noticed) - it sounds like it should work.

I'm curious why no debugging is showing up - perhaps you can add more debug() statements in the code and see if that helps any - or perhaps you need to make sure that /tmp/iwsend_mail.log exists on your system and is world-writable (chmod 666) just in case there was an access problem writing out the debugging data.

You should be guaranteed to get at least one debugging message for success or failure of sending the email.

--fish
(Interwoven Senior Technical Consultant)

fonttable.tbl.txt

output_connector_setting.png

text_in_pdf.png

text_in_msword.png

JackIntheBox

I created the log file, and now the debug log has entries only when I run it from the command line -- a success message.

I looked at KB 49413 here:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49413

and modified my sendmail script to include those suggestions, but still no dice.I have enclosed the latest send mail script. Can anyone please suggest anything??

Adam Stoller

Please make sure to fix syntactic errors with the script before posting it - the one you posted has an error on line 80 where you left out a '#' which was supposed to make part of the line a comment rather than parsed code.

I seriously doubt that you were able to run it from the command line - and it would not work from within a workflow either.

You will still probably get a warning from Mail::Mailer about an uninitized variable on line 210 (or thereabouts) - which you can ignore.

As I suggested before - please add LOTS of debug() messages throughout the code - so that we can get some idea from the debug log file how far it got and what information was being passed along.

I cannot really help you too much more regarding this as I am not in your environment and cannot see what is actually happening.

--fish
(Interwoven Senior Technical Consultant)

JackIntheBox

Yes, you are right. When I commented out the site specific information I posted the wrong version to the board. However, the fact still remains that I am able to run it from the command line and not from the Workflow. I have opened a support case and they are working on it as we speak. Thanks for all your help.

TEAMS SR Integration documentation.docx

vvs

Check the KB 49413 article which may help you.