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] omni logs are incorrectly displaying wrong timestamp (talos does show correct) #818

Open
1 task done
mdiskin opened this issue Jan 8, 2025 · 3 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@mdiskin
Copy link

mdiskin commented Jan 8, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Machine Logs view shows Date incorrectly:
image0

Sames logs using taloscli show correct.
image1

Expected Behavior

Expect same date to show.

Steps To Reproduce

talos 1.9.1/ pi cm4/rk1

What browsers are you seeing the problem on?

Chrome

Anything else?

No response

@mdiskin mdiskin added the bug Something isn't working label Jan 8, 2025
@smira
Copy link
Member

smira commented Jan 8, 2025

This relates to the lack of proper RTC on SBCs. The time is not set on boot until NTP kicks in, so both versions reconstruct timestamp, but at different times, so the time is accurate both ways, but accurate at the moment the log was sent, or the moment log was retrieved.

@mdiskin
Copy link
Author

mdiskin commented Jan 9, 2025

That makes sense. I have a turningpi board so thought the bmc would facilitate the right time. I do after boot and assuming ntp that log entries days later still coming in with 1970.

@smira
Copy link
Member

smira commented Jan 9, 2025

I don't know any specific information, if it does have RTC, then the driver might be missing in the kernel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants