Products | Versions |
---|---|
TIBCO LogLogic Enterprise Virtual Appliance | 6.3.0 |
TIBCO LogLogic Log Source Packages | LSP 35 and LSP 36 |
An issue has been discovered with systems that have LSP 35 with LMI 6.3.0 installed where parsed data reports and classic alerts use UTC time even after the system time is set to a local time zone. This causes the scheduled reports and alerts to trigger at UTC time instead of the local system time that is configured. This issue appears only in LSP 35 and does not have any impact on systems running an older LSP/LMI version. In order to fix this, a modification needs to be made to the my.cnf file which forces MySQL to use the system's configured local time zone.
#!/bin/bash echo newTimeZone $1 find /loglogic/ -type f -name "my.cnf*" | xargs sed -i 's|default-time-zone|#default-time-zone|g' find /loglogic/ -type f -name "my.cnf*" | xargs sed -i "/\#default-time-zone/a $1" find /loglogic/ -type f -name "my.cnf*" | xargs sed -i '/#default-time-zone/d' mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql mysql
Ex: ./changeMysqlTimeZone.sh "default-time-zone=EST"
$ cat /loglogic/conf/my.cnf.* | grep default-time-zone
Note: This is a temporary fix for systems running LMI 6.3.0 with LSP version 35, and this issue will be resolved in the later releases of LMI. Upgrading only LSP will not resolve the issues, users will need to upgrade both the LMI and LSP to have a permanent fix.