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

Wrong time when I use command user:lastseen or files:transfer-ownership #30387

Closed
ParametricIce opened this issue Dec 23, 2021 · 4 comments
Closed
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug needs info

Comments

@ParametricIce
Copy link

ParametricIce commented Dec 23, 2021

  1. When I use the command:
    occ user:lastseen admin
    It returns incorrect time. (-3 hours from my local time)
    Example output:
    admin last login: 23.12.2021 05:33
    But now system time is 23.12.2021 08:33

  2. Also when I transfered a files the time is incorrect.
    occ files:transfer-ownership user1 user2
    Example of folder name in mailbox's user2:
    transfered from user1 on 2021-12-23 07-00-52
    But now system time is 2021-12-23 10-00-52

Server has the correct time.
Log files have the correct time.
So my local TimeZone is UTC+03:00. And I think the above commands don't include the TimeZone (UTC only).

Server configuration

Operating system:
Centos
Web server:
Apache
Database:
Mariadb
PHP version:
7.4
Nextcloud version:
21.0.7

@ParametricIce ParametricIce added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Dec 23, 2021
@kmotseki
Copy link

I am experiencing the same issue on Nextcloud 24.0.5. lastseen result is 2 hours behind. 'logtimezone' is set correctly. php.ini set to correct timezone. Server (Ubuntu 20.04 LTS) set to correct timezone, MySQL set to use system timezone.

@szaimen
Copy link
Contributor

szaimen commented Jan 23, 2023

Hi, please update to 24.0.9 or better 25.0.3 and report back if it fixes the issue. Thank you!

My goal is to add a label like e.g. 25-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort!

If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+

@joshtrichards
Copy link
Member

Related: #44641

@nooblag
Copy link
Contributor

nooblag commented Jul 23, 2024

Yes, please, I have a PR open to address this problem, but the developers seem to have strong views about hardcoding UTC. Any help convincing them to change their mind would be useful :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug needs info
Projects
None yet
Development

No branches or pull requests

5 participants