cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

How do I rotate the wrapper log file?

joost_van_der_k
Inactive

On a production CSS platform, there is a large (1GB) log file at "D:\Program Files\Dynatrace\RUM Console\cva\eclipse\bin", called wrapper.


a) Why isn't this rotated?

b) Why is this logfile in a bin dir?



Actions taken:

Logfile rotated manually.

There is some info on this file at link:

<quote>

Getting support data when RUM Console is down

Manually collect and
compress the following directories and files:


  1. <RUM Console installation directory>\cva\eclipse\configuration\wrapper.conf

  2. <RUM Console installation directory>\cva\eclipse\version.xml

  3. <RUM Console installation directory>\cva\eclipse\workspace\configuration\database.properties

  4. <RUM Console installation directory>\cva\eclipse\workspace\logs

  5. C:\ProgramData\Compuware\Security Client\css.dat or
    C:\ProgramData\Dynatrace\Security Client\css.dat



    where <RUM Console installation directory> is by default either C:\Program Files\Compuware\RUM Console or
    C:\Program Files\Dynatrace\RUM Console

</quote>

The wrapper.conf file in the path mentioned in the documentation doesn't seem to govern this particular wrapper log file, as modifications to it and restarting the CSS, do not seem to affect the wrapper log file.

There are other wrapper.conf files in the <RUM Console installation directory>\cva\eclipse\ tree, but none seem to affect this wrapper log file.

How do I configure log rotation for the wrapper log file at "D:\Program Files\Dynatrace\RUM Console\cva\eclipse\bin"?

wrapper-log-file-contents.txt

3 REPLIES 3

adam_piotrowicz
Dynatrace Pro
Dynatrace Pro

Joost,

That looks like log file, but shoudl not be in /bin directory.

Please log a support ticket for this with example you just attached and RUM console support pack.

joost_van_der_k
Inactive

Cheers Adam, will do.

joost_van_der_k
Inactive

Question answered through support ticket:

https://community.dynatrace.com/community/display/...

This issue is known for 12.3.0 and solved in 12.3.3.