[Bug]: dashboard Online duration is displayed as negative time.

[ideaxy]

Describe the bug

dashboard Online duration is displayed as negative time.

Environment

• OS Version and CPU Arch(uname -a):
  Linux localhost.localdomain 6.12.0-1.23.3.2.el9uek.x86_64 Bump mysql-connector-python from 8.0.6 to 9.1.0 in /tools/upgrade seekdb#1 SMP PREEMPT_DYNAMIC Tue May 13 17:24:00 PDT 2025 x86_64 x86_64 x86_64 GNU/Linux

• OB Version(LD_LIBRARY_PATH=../lib:$LD_LIBRARY_PATH ./observer -V):
  observer (OceanBase SeekDB 1.0.0.0)
  REVISION: 100000262025111218-5343637512e28c346f938516af53b7879d4d5974

OBShell 4.3.3.0 (for OceanBase_CE)
REVISION: 12025110521-096c1eb4aa9798f07d63ff729f1cc5c024c3f08e

• Hardware resource(cpu core/memory size/disk hardware):

Fast Reproduce Steps(Required)

1. Log in to the obshell dashboard.
2. Check the Startup Time and Online Duration. The Startup Time is displayed as a future time, and the Online Duration is displayed as negative time.

Steps to reproduce the behavior:

Expected behavior

Actual Behavior

Online Duration-7h32m7s --

Additional context

seekdb for docker

[longdafeng]

Thanks for your feedback.

[Junkrat77]

Thank you for your feedback on this issue. We have already investigated the problem. The root cause was found to be the inconsistency of time zones among the container, cluster, and host machine. There are two specific issues:

1. The displayed startup time is in the future. This is because the obshell server retrieves the startup time from an internal table in the cluster (UTC+8). When returning this time to the dashboard, it carries the time zone of the container (UTC+0), while the dashboard displays it according to the time zone of the browser’s host machine (UTC+8). This mismatch leads to the startup time showing as a future moment.

2. The online duration is negative. This happens because obshell server calculates the online duration by subtracting the recorded startup time in the cluster (UTC+0) from the current container time (UTC+0), which results in a negative value.
   You can temporarily resolve this issue by mounting the time zone file when starting the seekdb Docker container:
   docker run -p 2881:2881 -p 2886:2886 -d -v /usr/share/zoneinfo/Asia/Shanghai:/etc/localtime oceanbase/seekdb

We will fix this issue in the next iteration.