Skip to main content
Solved

Unexplained difference between left-side column timestamp (Nodes view) and tooltip timestamps

  • April 15, 2026
  • 5 replies
  • 32 views

BugHunter42
Forum|alt.badge.img

Hello.

I noticed there is a weird difference between the two timestamps shown in Rundeck 5.19 web interface.

I’m referring tot he HH.mm:ss timestamp shown in the left sidebar, which I assume to be the server’s timestamp in local timezone and the ISO8601 timestamp shown in tooltip/.rdlog file. The problem is they look inconsistent so I was wondering how each of these timestamps is determined

 

The timestamp form tooltip/.rdlog file has a Zulu suffix which suggest UTC but there is a huge inconsistency


The server is located in France (UTC + 2), locale timezone is set correctly in the OS, so is the UTC clock. NTP synchronization is active. Therefore on Rundeck server, both local timezone and UTC are set correctly.

Rundeck JVM is executed with the correct timezone parameter “-Duser.timezone=Europe/Paris”. But the problem is there is much more than 2 hours differences between the left sidebar timestamp and the ISO8601 tooltip timestamps.

I noticed the issue issue in job during it’s execution on the 8 of April, before it ends (but the incesistcy remained after the job ended). The left-hand timestamp showed 09.02:11AM (of the 8 of April since the job keps executing overnight until the 8) while tooltip showed 2026-04-07T19:02:11Z for the same step/line of execution logs. That’s +14 hours… and that’s the case for pretty much all lines of logs of that job I’ve checked. So definitely not just a local timezone versus UTC.
 

I’m wondering whether that timestamp comes from the server clock or the remote node clock or elsewhere that might explain this weird 14 hours difference. Any useful info that helps me understanding this inconsistency is welcome.

Best answer by MegaDrive68k

Hi ​@BugHunter42 that’s a regression, I’ve tested 5.20 and isn’t honoring the -Duser.timezone param. (it works on 3.x and 4.x. old branches). I’m opening an internal ticket to solve this. Thanks for your feedback!

5 replies

Forum|alt.badge.img
  • PagerDuty Team 📟
  • Answer
  • April 15, 2026

Hi ​@BugHunter42 that’s a regression, I’ve tested 5.20 and isn’t honoring the -Duser.timezone param. (it works on 3.x and 4.x. old branches). I’m opening an internal ticket to solve this. Thanks for your feedback!


BugHunter42
Forum|alt.badge.img
  • Author
  • New Member đź‘‹
  • April 16, 2026

Hello,

Thanks for confirming the bug :D


BugHunter42
Forum|alt.badge.img
  • Author
  • New Member đź‘‹
  • April 16, 2026

PS : I think this question can be tagged as resolved but I have no idea how to do that on this forum


xamici
Forum|alt.badge.img+1
  • Community Manager đź’š
  • April 16, 2026

Hi ​@BugHunter42, there’s a “best answer” gray button below the text. I marked that off, so no worries.

See you around!


BugHunter42
Forum|alt.badge.img
  • Author
  • New Member đź‘‹
  • April 16, 2026

​@xamici Thanks