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_##.txtIt seems that the log files are being rotated but the trace files are not. Is this a known bug?
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.
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.)
I confirmed that this problem is fixed in v12.1.2.
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