Perl warnings and OD deployment status in iwtrace.log

ENV: Solaris 8, Teamsite 6.5 SP3,

We have noticed in last few days that the size of our iwtrace log is increasing very fast day by day. The reason behind that it is logging some unnecessary Perl warnings messages. We have also noticed that when we run system commands like “iwodcmd” and run the deployment through IPLS or workflow, it is logging the deployment status into iwtrace log.

Can we configure logging in iwtrace.log so that we can restrict Perl warning and OD deployment status messages

__________________________________________________________________
Use of uninitialized value in concatenation (.) or string at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_generate_xml_binaries.ipl line 291.
Prototype mismatch: sub main::getJSP vs () at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_update_db_submission.ipl line 1043.
Use of uninitialized value in concatenation (.) or string at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_generate_xml_binaries.ipl line 291.
Prototype mismatch: sub main::getJSP vs () at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_update_db_submission.ipl line 1043.
"my" variable @events masks earlier declaration in same scope at (eval 62) line 112.

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment sales_extranet/SalesExtranetDeploy.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment sales_extranet/SalesExtranetDeploy finished:
ID: m3384 Start time: Fri Dec 28 12:38:55 EST 2007
Status: Completed
Status details:
All targets got completed status

[Tue Jan 22 09:47:43 2008] Too many arguments for command /opt/iw-home/iw-perl/bin/iwperl (args: 1063, max: 510)
[Tue Jan 22 09:48:43 2008] Too many arguments for command /opt/iw-home/iw-perl/bin/iwperl (args: 1063, max: 510)
[Tue Jan 22 09:49:43 2008] Too many arguments for command /opt/iw-home/iw-perl/bin/iwperl (args: 1063, max: 510)

Any pointers will be appreciated.
Regards
Vinay Kumar

Find more posts tagged with

Comments

moonkhanna

Check your deploy.cfg file as well as odbase.xml as well as your deployment Configuration xml. Somewhere you would have configured, your iwtrace.log to be your deployment log. Remove that entry and replace with the right entry.

restart your OD services..

Bhargav Coca

Do you already have a submit.cfg configured for your environment? Do you see lot of stuff related to submit.cfg in your Iwtrace.log??

Thanks

Adam Stoller

ENV: Solaris 8, Teamsite 6.5 SP3,

We have noticed in last few days that the size of our iwtrace log is increasing very fast day by day. The reason behind that it is logging some unnecessary Perl warnings messages. We have also noticed that when we run system commands like “iwodcmd” and run the deployment through IPLS or workflow, it is logging the deployment status into iwtrace log.

Can we configure logging in iwtrace.log so that we can restrict Perl warning and OD deployment status messages

__________________________________________________________________
Use of uninitialized value in concatenation (.) or string at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_generate_xml_binaries.ipl line 291.
Prototype mismatch: sub main::getJSP vs () at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_update_db_submission.ipl line 1043.
Use of uninitialized value in concatenation (.) or string at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_generate_xml_binaries.ipl line 291.
Prototype mismatch: sub main::getJSP vs () at /opt/iw-home/custom/sales_extranet/perl/sales_extranet_update_db_submission.ipl line 1043.
"my" variable @events masks earlier declaration in same scope at (eval 62) line 112.

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment sales_extranet/SalesExtranetDeploy.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment sales_extranet/SalesExtranetDeploy finished:
ID: m3384 Start time: Fri Dec 28 12:38:55 EST 2007
Status: Completed
Status details:
All targets got completed status

[Tue Jan 22 09:47:43 2008] Too many arguments for command /opt/iw-home/iw-perl/bin/iwperl (args: 1063, max: 510)
[Tue Jan 22 09:48:43 2008] Too many arguments for command /opt/iw-home/iw-perl/bin/iwperl (args: 1063, max: 510)
[Tue Jan 22 09:49:43 2008] Too many arguments for command /opt/iw-home/iw-perl/bin/iwperl (args: 1063, max: 510)

Any pointers will be appreciated.
Regards
Vinay Kumar

Migrateduser

Thanks Ghoti,

Thanks for your help. Will follow the same steps and update you accordingly.

Regards
Vinay

Migrateduser

Thanks moonkhanna

I couldnt find iwtrace related entries in deploy.cfg ,odbase.xml ,deployment Configuration xml files .

Please let me know if we can search these settings in some more related files.

Regards
Vinay

chicka

Thanks moonkhanna

I couldnt find iwtrace related entries in deploy.cfg ,odbase.xml ,deployment Configuration xml files .

Please let me know if we can search these settings in some more related files.

Regards
Vinay

Do you have any customized scripts to initiate the deployment process and check the logging is pointed to iwtrace log file.

ISCBorisB

Do you have any customized scripts to initiate the deployment process and check the logging is pointed to iwtrace log file.

It really helps to read what has been already posted before chiming in.
As has been already noted by Ghoti, from the very first post you can get custom script name and even point of failure

moonkhanna

Thanks moonkhanna

I couldnt find iwtrace related entries in deploy.cfg ,odbase.xml ,deployment Configuration xml files .

Please let me know if we can search these settings in some more related files.

Regards
Vinay

Vinay - is this happening just some deployments or for all deployments? Which script are you rinning in your workflows to instantiate the deployments? If this happening only for deployments initiated by your custom scripts..then its something related to what Adam already stated..

If this is happening for all deployments.. then it something with your config files.. to test this, run a deployment directly from your OD server or OD admin server and see if iwtrace.log has its log..