Page 1 of 1

What are dstage_wrapper_trace_2.log files?

Posted: Mon May 24, 2010 1:40 pm
by ajaykumar
I dont know why the trace files are coming in this home/dsadm/ds_logs/-rw-rw-r-- 1 dsadm dstage 527 2009-07-21 14:31 dstage_wrapper_trace_1.log
-rw-rw-r-- 1 dsadm dstage 527 2009-07-21 14:31 dstage_wrapper_trace_2.log
-rw-rw-r-- 1 dsadm dstage 527 2009-07-21 15:49 dstage_wrapper_trace_3.log
-rw-rw-r-- 1 dsadm dstage 527 2009-07-21 15:49 dstage_wrapper_trace_4.log
-rw-rw-r-- 1 dsadm dstage 527 2009-10-15 10:46 dstage_wrapper_trace_5.log
-rw-rw-r-- 1 dsadm dstage 527 2009-10-15 11:19 dstage_wrapper_trace_6.log
-rw-rw-r-- 1 dsadm dstage 527 2009-10-15 12:49 dstage_wrapper_trace_7.log
-rw-rw-r-- 1 dsadm dstage 527 2009-12-14 15:17 dstage_wrapper_trace_8.log
-rw-rw-r-- 1 dsadm dstage 527 2009-12-14 15:17 dstage_wrapper_trace_9.log
-rw-rw-r-- 1 dsadm dstage 527 2010-02-18 14:02 dstage_wrapper_trace_10.log
-rw-rw-r-- 1 dsadm dstage 527 2010-02-18 14:03 dstage_wrapper_trace_11.log
-rw-rw-r-- 1 dsadm dstage 527 2010-05-18 10:30 dstage_wrapper_trace_12.log
-rw-rw-r-- 1 dsadm dstage 527 2010-05-18 10:36 dstage_wrapper_trace_13.log
-rw-rw-r-- 1 dsadm dstage 527 2010-05-18 10:37 dstage_wrapper_trace_14.log

If i open any trace file, here is the output

2010-02-18 14:02:49,317 WARN com.ascential.xmeta.util.config.impl.file.FlatFileConfiguration.getPropertiesFileURL(FlatFileConfiguration.java:472) - Ambiguity detected for the configuration file xmeta.bootstrap.properties. The file was found in the following locations: file:/opt/IBM/InformationServer/ASBNode/conf/xmeta.bootstrap.properties, file:/opt/IBM/InformationServer/ASBNode/conf/xmeta.bootstrap.properties
2010-02-18 14:02:49,587 INFO com.ascential.dstage.proxies.NewRepos.Init(NewRepos.java:837) - Locking is enabled

Can any one tell me the solution for this issue

Posted: Mon May 24, 2010 2:15 pm
by ray.wurlod
There is no issue, and therefore there is no "solution".

Up to 20 of these dstage_wrapper_trace logs are written into the ds_logs directory in the home directory of dsadm. It's simply a matter of "that's how it works".

The message about duplicate xmeta.bootstrap.properties is spurious (a bug) - you will note that the "two" files have identical pathnames.