Forum Discussion

Landono's avatar
Landono
Icon for Nimbostratus rankNimbostratus
Nov 06, 2014

/var/log/ltm using incorrect timezone

We noticed today that all of our F5 LTM devices (6 2000's and 6 4000's) have the incorrect timezone for the /var/log/ltm file. We are in the Moutain timezone, but all of the log entries are 14 hours ahead of what they should be. We have NTP running correctly, and if you run date from the command line it shows the correct time and date. We even have an iRule that logs access log messages and they have the correct timestamp, pulled from [clock format [clock seconds] -format "%d/%b/%Y:%H:%M:%S"].$fract $zone. Since we're seeing it on all of our boxes, I'm assuming it's just a configuration setting that we have that's incorrect.

 

Here's an example of an access log-styled entry:

 

Nov 7 04:58:27 lb1 info tmm[12630]: Rule /Common/http_logger : 1.1.1.1 2.2.2. [06/Nov/2014:14:58:27.915 -0700] "GET website.com" 200 - 397 - "" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0)"

 

The correct time is Nov 6. 14:14, so the timestamp that says Nov 7 04:58 is incorrect. Any idea what could be causing this?

 

application delivery
logging
LTM
management

2 Replies

Sort By
  • R_Eastman_13667's avatar
    R_Eastman_13667
    Historic F5 Account
    Nov 07, 2014

    In the management GUI: System >> Platform >> Time Zone. Set the value to US/Mountain.

     

  • R_Marc's avatar
    R_Marc
    Icon for Nimbostratus rankNimbostratus
    Nov 10, 2014

    Interesting. I only have a few 4K's, so I went to look. Sure enough I see a similar problem.

    Nov 10 16:05:38 bip info tmm5[9877]: Rule /Common/****** : 10/11/2014 16:05:38 -0800 10.0.0.1:35410

[user@bip:Active:In Sync] log  date
Mon Nov 10 18:05:41 CST 2014

    It's not 14 hours off like yours, but still off. I think this is worthy of a ticket.

    This is running: Version 11.4.1 Build 635.0