Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] log timestamp is still in UTC despite log.local_time: true #7359

Closed
4 tasks done
mangkoran opened this issue Oct 18, 2024 · 1 comment
Closed
4 tasks done

[bug] log timestamp is still in UTC despite log.local_time: true #7359

mangkoran opened this issue Oct 18, 2024 · 1 comment

Comments

@mangkoran
Copy link

Prerequisites

Platform (OS and CPU architecture)

Linux, ARM64

Installation

Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)

Setup

On a router, DHCP is handled by the router

AdGuard Home version

v0.107.53

Action

Set log.local_time to true in config file

Expected result

Log use local time format

Actual result

Log use UTC format

Additional information and/or screenshots

wezterm-gui_CbTRHUPoQ4

@mangkoran mangkoran changed the title log timestamp is still in UTC despite log.local_time: true [bug] log timestamp is still in UTC despite log.local_time: true Oct 18, 2024
@mangkoran
Copy link
Author

I think I have found the root cause/solution thanks to #6376 (comment), daeuniverse/dae#345 (comment).

Because golang use local zoneinfo file to identify the timezone12 and relate package is not install by default at OpenWrt, so if you want the log time correct at OpenWrt, you should install the zoneinfo package

tl;dr solution is to install zoneinfo-all package.

opkg update
opkg install zoneinfo-all

Then restart adguardhome or reboot system.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant