Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

utime went backwards! #5608

Closed
richvdh opened this issue Jul 3, 2019 · 2 comments
Closed

utime went backwards! #5608

richvdh opened this issue Jul 3, 2019 · 2 comments

Comments

@richvdh
Copy link
Member

richvdh commented Jul 3, 2019

Observed during startup:

2019-07-03 08:51:31,442 - synapse.util.logcontext - 381 - ERROR - None - utime went backwards! 0.000000 < 1.108000
2019-07-03 08:51:31,445 - synapse.util.logcontext - 389 - ERROR - None - stime went backwards! 0.000000 < 0.096000

presumably related to #5499 / #3548
@richvdh
Copy link
Member Author

richvdh commented Jul 3, 2019

only seems to happen when synapse is set to daemonize

richvdh added a commit that referenced this issue Jul 3, 2019
@richvdh
Fix 'utime went backwards' errors on daemonization.
c430d46 
Fixes #5608
@richvdh richvdh mentioned this issue Jul 3, 2019
Merged
@richvdh
Copy link
Member Author

richvdh commented Jul 3, 2019

fixed by #5609

@richvdh richvdh closed this as completed Jul 3, 2019
hawkowl pushed a commit that referenced this issue Jul 3, 2019
@richvdh @hawkowl
Fix 'utime went backwards' errors on daemonization. (#5609)
cb8d568 
* Fix 'utime went backwards' errors on daemonization.

Fixes #5608

* remove spurious debug
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@richvdh