Standard rolling trace on the WPs

[Legacy User]

Create a Timed Event that is repeated every X number of minutes. The X should be something like 3-5 minutes. Here is the script to use:

Process tab:
!Set a DB=4 and TCP/IP=2 trace on the WPs
!Get System Name
:SET &TRC# = GET_UC_SYSTEM_NAME()
!Turn on tracing for WPs
:SET_UC_SETTING SET_TRACE, &TRC#, "2400000000000000"

!Process tab:
!Get System Name
:SET &TRC# = GET_UC_SYSTEM_NAME()
!Turn off tracing on WPs
:SET_UC_SETTING SET_TRACE, &TRC#, "0000000000000000"
!Turn on tracing for WPs
:SET_UC_SETTING SET_TRACE, &TRC#, "2400000000000000"

Couple things to keep in mind. This will create 10 trace logs. After it reaches 10 they will start to roll off. So if you set the X as 3 minutes all 10 trace files would cover a range of 30 minutes. In other words, you would need to disable the trace within 30 minutes of the problem or the log with the error would roll off the server. Of course you can increase the X to a higher value but then you get huge trace files but they would cover a longer period of time.

[John O'Mullane]

Hi Ian,
I implemented this trace last week to troubleshoot an issue. 
I did it with an hourly event, knowing that the maximum number of logs I would have is 10.

This all worked fine.

When I stopped my event, I checked my disk space and was happy to see it had only reached 60%.

I got a call at the weekend saying our disk space had reached 100%.

Although no new trace logs were created after I stopped my Event, it looks like the existing trace files continued to build up with logs.

Is this expected behavior?

John.

[Anon Anon]

I suppose its a hmm lets say design to be improved :-)

content of the !PROCESS

!Turn off tracing on WPs
:SET_UC_SETTING SET_TRACE, &TRC#, "0000000000000000"
!Turn on tracing for WPs
:SET_UC_SETTING SET_TRACE, &TRC#, "2400000000000000"

As there is tracing stopped and started (to force creation of a new set of trace files) the creator of the script forgot to implement a logic setting all values to 0 after the time event is stopped.

[Anon Anon]

Here is the link to Trace scheduler
https://automic.force.com/support/apex/CommunityArticleDetail?id=kA4b00000004THR

i just discovered that the link to the binary is still outdated for more that 1,5 Years...

Possibly you can ask support to update the link, as its a part of the support site:

https://us.v-cdn.net/5019921/uploads/editor/vy/imvydr1v4bwz.jpg" width="674">

Maybe my old Friend Harald_Heidinger_152 could help in this case....

cheers Wolfgang

[John O'Mullane]

FrankMuffke Are you saying I should use the Trace Scheduler in future?

[John O'Mullane]

FrankMuffke btw, thanks for the update.

How can I set it back to 0?
Although I've removed the Trace files, every time I restarts the WP's a new trace get's created.

[Anon Anon]

JohnO'Mullane
You are welcome.

Just go to system Overview / Automation Engine - rightclick on a WP - Properties and set everything to 0

I there is everything 0 - then have a look on your UCSRV.INI file - Trace section and set here everything to 0 as well. - Don`t forget to restart your WPs.

Just FYI: Removing the Trace files does not prevent your AE from creating Trace Files!

[Anon Anon]

regarding Trace scripts - as far as I remember, the Trace schduler script was working fine.

you can ask Support as well, there are different rolling trace scripts available.

or you can create one for your own if you want :-)

[John O'Mullane]

FrankMuffke

Gotcha, we have manually set the trace to 0 on our Primary WP and everything looks good again.
I also spoke to Harriet_Kim_1764 from Support who shared this discussion with me initially.

I know know a lot more about Traces  :) 

[Anon Anon]

JohnO'Mullane
Good that everythings fine now.

The most important thing is to know the differences of both methods of activating traces:

A ) INI file - everytime the component is started the trace will be written, until INI file gets changed AND component will be restarted. If you  changed it  manually in system overview for the time its deactivated but as soon as component will be restarted writing traces will start again (as defined in INI file)!

B ) GUI (System overview) - trace will be written until component gets restarted OR settings will be changed back manually in system overview.

[John O'Mullane]

FrankMuffke

regarding this bit...
trace will be written until component gets restarted 

We restarted the WP's but this alone did not stop trace files from generating, also had to change properties of WP's in System Overview

[Anon Anon]

JohnO'Mullane

Did you enable Traces via GUI?

In this case I think (but I am not 100% sure) as long as any WP is still running the trace option will be "inherited" to newly started WPs.

If you stop ALL WPs and start them again traces should not be enabled again.

[John O'Mullane]

This was not our experience.
We set the trace initially via the Event mentioned at the start of this article.
We then stopped the Event and I can see why this would not necessarily stop the trace.
We then restarted the WP's but still found that trace options were still set when we edited WP1.

[Legacy User]

Hi JohnO'Mullane

My apologies, it should have also included a script that you can run to completely stop the rolling traces:

******************************** SCRI.STOP_ROLLING_TRACE - Process tab ******************************** ! ! Turn off ! !Set a DB=4 and TCP/IP=2 trace on the WPs !Get System Name :SET &TRC# = GET_UC_SYSTEM_NAME() !Turn off tracing for WPs :SET_UC_SETTING SET_TRACE, &TRC#, "0000000000000000"

[John O'Mullane]

Thanks Harriet_Kim_1764

[Legacy User]

You're welcome, JohnO'Mullane.  My apologies on the oversight.  Thanks again for bringing that to my attention.