All about timezones in LM

LicenseMonitor must be timezone-aware in 2 different situations:

1.  When parsing a debug log that was generated in a different timezone:

The debug log parser is executed locally on the LM server using the servers local timezone by default.  The debug log contains date/time information that was generated using the timezone of the remote server.  In the configuration, you can specify a timezone for the debug log.  What we do is run the debug log parser job in an environment that has the timezone overridden to the one that you specify.  Our parser will then appropriately localize the entries found in the log.  If the specified timezone is valid for your system, it should work just fine.  Example:

As you can see, I'm in EST, but when I override the environment with PST, the date/time is reported accordingly.  This is how we run the parser if an alternate timezone is specified in the configuration.  There are several supported timezone specifications on various systems.  Google is a good place to search for valid timezone specifications.  To confirm that the timezone override is working for your remote debug logs, find a DENIED event in the log and match that up with a denial in a history report for that tag.  If things are working correctly, the time for the denial should be localized to the LM server timezone.

2. When running lmstat across ssh on a machine located in a different timezone:

If you are using lmstat against a remote server directly, the timezone should already match what your LM server timezone is.  The lmstat utility reports the times using the timezone for the machine that it runs on.  If you are using lmstat across ssh, then you will need to override the timezone in the command setting.  Example:

In this case, demo5 is in PST, so that is what is reported when I run date on it across ssh.  But I can override it to EST to get the date to reflect my timezone.  The timezone specification in the monitor administration page only affects the optional debug log parsing.  It does not affect the lmstat run.

S, for a license server running in Europe, you're probably going to want to specify something like:

for the lmstat command to get the clock to not appear incorrect with respect to the LM server clock.

To summarize, with lmstat, you must make sure that it is executed in the LM server timezone.  With debug logs, you must make sure that the parser is executed in the timezone that the debug log was generated in.