TM1 Forum

Hi Fellows,

I finally had enough of GMT and decided to change my tm1s-log.properties to use local time...
So I placed tm1s-log.properties along side my tm1s.cfg file ( tm1s.cfg in under standard CX directory, DB / Logs directory on the other drive E:). Loggers set as below:

log4j.logger.TM1=DEBUG,S1
log4j.appender.S1=org.apache.log4j.SharedMemoryAppender
log4j.appender.S1.MemorySize=5MB
log4j.appender.S1.MaxfileSize=100mb
log4j.appender.S1.MaxBackupIndex=20
log4j.appender.S1.Timezone=local

Time stamp still shows GMT time, any ideas why?

I have converted GMT to local plenty of times before, so it strikes me why it suddenly stopped working.

Note: CX 10.2 / Win 08 R2 environment

Thanks in advance

Are you sure the box you are running the TM1 instance on is configured to use local time? I assume you're in Sydney, physically, but that doesn't guarantee the Windows setting.

I don't know if parameter values are case sensitive or not but I always used =LOCAL. Always worked for me, I have also seen cases where it stopped working and reverted to GMT but server restart always fixed it. Speaking of, you need to restart the server for the change to take effect which I guess you know.

The other thing which I'm sure you are aware of is that the name "tm1s-log.properties" is a misnomer. The timestamp in the tm1s.log file (transaction log) is ALWAYS in GMT and there is nothing you can do about that. The parameter only changes the timestamps logged in the tm1server.log file (server message log), in fact all the settings effect the message log and the file should really be called "tm1server-log.properties". I don't know whether the audit log timestamps in the Rawstore file are affected but I would assume not.

Because you can't change the timestamps in the transaction log although local time setting for the message log does make it more convenient to see when processes have been run it does mean there will be a time offset to the transaction log if data changes are being investigated.

rmackenzie wrote:Are you sure the box you are running the TM1 instance on is configured to use local time? I assume you're in Sydney, physically, but that doesn't guarantee the Windows setting.

Yeah mate, UTC + 10 (Melbourne, Sydney) is set to be the timezone on the box. The first thing I checked lol

lotsaram wrote:I don't know if parameter values are case sensitive or not but I always used =LOCAL. Always worked for me, I have also seen cases where it stopped working and reverted to GMT but server restart always fixed it. Speaking of, you need to restart the server for the change to take effect which I guess you know.

The other thing which I'm sure you are aware of is that the name "tm1s-log.properties" is a misnomer. The timestamp in the tm1s.log file (transaction log) is ALWAYS in GMT and there is nothing you can do about that. The parameter only changes the timestamps logged in the tm1server.log file (server message log), in fact all the settings effect the message log and the file should really be called "tm1server-log.properties". I don't know whether the audit log timestamps in the Rawstore file are affected but I would assume not.

Because you can't change the timestamps in the transaction log although local time setting for the message log does make it more convenient to see when processes have been run it does mean there will be a time offset to the transaction log if data changes are being investigated.

Upper case made no difference nor server start.

Oh yeah, I agree the naming convention is misleading.

The investigation goes on. Please feel free to thrown in ideas

Thanks

Hi EvgenyT,Any updates on the issue,Please Post. Thanks

No, haven't had any luck with it .... Are you experiencing similar problem?

Thanks for the reply,I am not experiencing this problem but would be thankful and happy to know the work around for this.

BariAbdul wrote:.... but would be thankful and happy to know the work around for this.

Me too

How about change DEBUG to INFO?

Actually, what I am using is below, you can give it a go.

macsir wrote:Actually, what I am using is below, you can give it a go.

Code: Select all

log4j.logger.TM1=INFO, S1

# S1 is set to be a SharedMemoryAppender
log4j.appender.S1=org.apache.log4j.SharedMemoryAppender
# Specify the size of the shared memory segment
#log4j.appender.S1.MemorySize=5 MB
# Specify the max filesize
#log4j.appender.S1.MaxFileSize=500 MB
# Specify the max backup index
#log4j.appender.S1.MaxBackupIndex=0
# Specify GMT or Local timezone
log4j.appender.S1.TimeZone=Local

Thanks mate, but it didnt help... Im really puzzled here

Further to this thread, it's not just TimeZone logger that refuses to work.

I have recently added log4j.logger.TM1.Cube.Stargate = DEBUG and log4j.logger.TM1.Cube.Stargate.Reference = DEBUG; played around with VM/VMT setting and calculated few heavy view: No references in the log whatsoever

I am starting to wonder if it's version related CX 10.2.1.1...

We also have this problem, the timestamps in the tm1server.log file are in GMT time.

This IBM tech note http://www-01.ibm.com/support/docview.w ... wg21459102 states..

"NOTE: Changing the log4j.appender.S1.TimeZone to LOCAL will not change what's in the actual log file on disk. This is always recorded in GMT. It does change the times to local time when you view the log file via Architect. "

We don't use Architect so I find this confusing how does this product render the timestamps in the correct format? I'm assuming based on this no one actually found a way to resolve this?

Stuart wrote:We also have this problem, the timestamps in the tm1server.log file are in GMT time.
....
I'm assuming based on this no one actually found a way to resolve this?

EvgenyT wrote:Further to this thread, it's not just TimeZone logger that refuses to work.

I have recently added log4j.logger.TM1.Cube.Stargate = DEBUG and log4j.logger.TM1.Cube.Stargate.Reference = DEBUG; played around with VM/VMT setting and calculated few heavy view: No references in the log whatsoever

We have both of them (Timezone, Stargate) working in our dev environment. I did a quick test with a brand new TM1 instance and verified that, setting the TimeZone to local, actually changes the timestamps in the tm1server.log to the local timezone. See screenshot, attached.

tm1s-log.properties needs to be in the same folder where tm1s.cfg is present. Can you confirm where you have placed the tm1s-log.properties file?

Stuart wrote:We also have this problem, the timestamps in the tm1server.log file are in GMT time.

This IBM tech note http://www-01.ibm.com/support/docview.w ... wg21459102 states..

"NOTE: Changing the log4j.appender.S1.TimeZone to LOCAL will not change what's in the actual log file on disk. This is always recorded in GMT. It does change the times to local time when you view the log file via Architect. "

We don't use Architect so I find this confusing how does this product render the timestamps in the correct format? I'm assuming based on this no one actually found a way to resolve this?

Local Timezone logging works, or at least I have never seen it not work. The link to the documentation you posted is referring to the transaction log file; the tm1s.log. NOT the tm1server.log (message log).

The message log can be changed to local time. The transaction log can't. That's what the documentation is meaning.

Note that although most config changes to tm1s-log.properties are picked up instantly the Timezone toggle does require a restart of the tm1 instance to take effect.

Yeah I still have this problem with the GMT timestamp within the tm1server.log file. Our server is AIX 7.1 and we are running TM1 10.2 FP1.

Files tm1s.cfg and tm1s-log.properties are located within:
/opt/ibm/cognos/model/config

tm1s-log.properties contains the entry
log4j.appender.S1.TimeZone=LOCAL

Maybe its case sensitive? If I type date via putty on the AIX server it returns the correct timezone.

Have you tried raising a case with support to address this issue?

Yes I logged a support ticket yesterday and can now confirm that log4j.appender.S1.TimeZone=Local does not work for AIX.

PM07746

Problem description

When Log4J Timezone is set to Local, it works on Windows but
does not work on AIX..Below is how it is set in tm1s-log.properties file.

log4j.appender.S1.TimeZone=Local

There is no intent to address the issue raised in this APAR
Problem is in the LOG4CXX library which is a third party library.
Currently we have no plans to upgrade to a newer version of the LOG4CXX library and no guarantee that this problem is corrected in latter versions of the product.