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

Logs do not show up in /admin/logs #4921

Closed
shalak opened this issue Dec 22, 2023 · 3 comments
Closed

Logs do not show up in /admin/logs #4921

shalak opened this issue Dec 22, 2023 · 3 comments

Comments

@shalak
Copy link

shalak commented Dec 22, 2023

I've configured a docker-compose setup, using NathanVaughn's image.

Everything was working correctly, then, for testing purposes, I changed the config.ini.php entry od dbpass to something wrong. After recreating the containers, it failed to work, as expected. Then I changed it back to the correct password. Please bare in mind that this might be unrelated to the issue, I don't know.

Now, I noticed that there are no logs visible in /admin/logs page. It simply says No records to display.

I connected to the DB using phpMyAdmin and the SELECT * FROM wt_log ORDER BY wt_log.log_time DESC shows the logs, including new ones.

What's going on here? Any ideas on how to debug this?

@shalak
Copy link
Author

shalak commented Dec 23, 2023

Huh, today (12:01 CET) it started to work.

I just recalled that around the time the logs stopped working, I noticed that containers are on UTC, so I mounted /etc/localtime. First to the app container (the logs were not showing by then) then to the DB container (still not showing) - also I'm in CET and it was just after midnight my time (i.e. before mounting localtime the containers were on 22nd of December and after the mount they were on 23rd).

I believe this might be related...

@miqrogroove
Copy link
Contributor

There is a major bug in the log filtering subsystem. See #4549

Basically, the 'dates', even the default ones, in the log filter are treated as UTC times and then converted incorrectly to a SQL criteria.

I've written an excellent patch and it's attached to that issue if you want to try it. As for this issue, I think it can be closed as a duplicate.

@shalak
Copy link
Author

shalak commented Dec 23, 2023

Duplicate of #4549

@shalak shalak closed this as not planned Won't fix, can't repro, duplicate, stale Dec 23, 2023
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

2 participants