v12.1 service manager does not rotate trace files.

Discussion created by Michael_Lowry on Dec 8, 2017
Latest reply on Jan 9, 2018 by Michael_Lowry

Like • Show 0 Likes0
Comment • 6

In the ucybsmgr.ini file, I have the following trace settings:

[TRACE] file=/var/uc4/servicemanager-server/SMgr_EXP2_trc_##.txt trccount=100 tcp/ip=9 cmd=9

In /var/uc4/servicemanager-server, I see the following files:

SMgr_EXP2_log_00.txt SMgr_EXP2_log_01.txt SMgr_EXP2_log_02.txt SMgr_EXP2_log_03.txt SMgr_EXP2_trc_##.txt

It seems that the log files are being rotated but the trace files are not. Is this a known bug?

Outcomes

6 Replies

Paul_Smith_9332 Dec 15, 2017 2:45 PM
Hi Michael,
I did a quick search through our system for any errors like that, but didn't find anything.
I would recommend opening a ticket.
All the best,
Cameron
Like • Show 0 Likes0
Actions
Michael_Lowry Dec 15, 2017 3:05 PM
Paul_Smith_9332: Thanks for checking. I opened INC00217296 for this.
Like • Show 0 Likes0
Actions
Karin_Wasinger_8156 Dec 15, 2017 3:20 PM
Actually none of the Automic components rotate the trace files as it is the case with logfiles. Traces - as soon as switched on - will write to the same file until switched off.

However there is one exception: Since v12 the memory trace can be defined with a defined size, where a trace of a defined size will be written as soon as a specific u-number is occuring within a serverprocess, but that is for the Automation Engine only, and is also not really a fileswitch.
Like • Show 0 Likes0
Actions

Michael_Lowry Dec 15, 2017 3:45 PM

Karin Wasinger wrote:

Actually none of the Automic components rotate the trace files as it is the case with logfiles. Traces - as soon as switched on - will write to the same file until switched off.

This is not correct. The Automation Engine rotates both logs and traces whenever logging is changed or the process stops and restarts. It renames old logs & traces and begins writing new ones.

The SMgr documentation clearly states that the service manager works the same way.

[                                                   TRACE                                                   ]

file=
The path and the file name of the trace file.

Any file name for a text file with several place holders for current system information:

$$ is replaced by server process type (WP or CP) in the context of a server process.

* is replaced by the three-digit process number in the context of a server process.

## is replaced by 00 after the available trace files' corresponding numbers have been raised by one during startup of a trace.

*** is replaced by the three-digit abbreviation of the respective unix version (unix agent only).
...
Default:                                                                  ../temp/trace_##.txt

(Emphasis mine.)

Actions

Michael_Lowry Dec 15, 2017 4:20 PM
I think we have a misunderstanding of what rotation means. By rotation, I simply mean the process of moving old files out of the way before new files are written. I realize that the Service Manager does not rotate files automatically based on predefined criteria like file size or elapsed time. However, it does (or should) rotate the files when the program is stopped and restarted. This is what is not working correctly. The program rotates logs files, but it does not rotate traces. In fact, it does not even name the first trace file correctly.
Like • Show 1 Like1
Actions
Michael_Lowry Jan 9, 2018 9:55 AM
Problem PRB00217357 has been opened for this bug.
Like • Show 0 Likes0
Actions

v12.1 service manager does not rotate trace files.

Outcomes

Related Content

Recommended Content