Forum Discussion
helenio
Nimbostratus
NimbostratusWrong date/clock for cached objects in RAMN Cache
Hello, I don't understand why the system clock is correct but cache object have 2h delay. I did the command fate just after I deleted the Cache of the LB therefore the object should be fresh
~ date Wed Jun 11 08:09:41 CEST 2014
(cfg-sync Changes Pending)(Active)(/Common)(tmos) show ltm profile ramcache /Common/Myprofile Ltm::Ramcaches /Common/Myprofile
Host: mysite.xx.ch URI : /_layouts/images/myimage.png
Source Slot/TMM 1/0 Owner Slot/TMM 1/1 Rank 1
Size (bytes) 581 Hits 19
Received 2014-06-11 06:09:52
Last Sent 2014-06-11 06:13:46
Expires 2014-06-12 06:09:52
Vary Type none
Vary Count 1
Vary User Agent none
Vary Encoding none
What_Lies_Bene1Cirrostratus
Perhaps the time used is UTC and it works out the valid date etc. via the configured timezone? Are you +- 2hrs from UTC?
helenioZone is seams correct
sys ntp { servers { xx.xx } timezone Europe/Zurich }
system date too:
[Active:In Sync] ~ date Wed Jun 11 11:10:04 CEST 2014
- What_Lies_Bene1
OK so that confirms it. The output of the show command is displaying the UTC/GMT time, not the 'local' time. It's an output error that I'm sure you can ignore OR this feature works with UTC only and ignores the timezone in all cases which means it works just fine anyway.
- helenio
Yes i suppose that cached object are stored with UTC/GMT. Thabnks'
- What_Lies_Bene1You could always do a quick test, set the expiry to 1hr then connect and see if you get any cache hits.