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] - cardano-node relay on MacOS sometimes dies with SystemClockMovedBack error #2138

Closed
stakelovelace opened this issue Nov 28, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@stakelovelace
Copy link

I've been running latest master build of cardano-node on my Macbook for a while, every now and then the node just dies - the command prompt from where it was launched shows:

cardano-node: ExceptionInLinkedThread "ThreadId 41" (SystemClockMovedBack (SlotNo 14912403) (SlotNo 14912400))

Given I don't actually do any clock adjusting on my laptop, would be good to know what's causing it and how to avoid it.

@stakelovelace stakelovelace added the bug Something isn't working label Nov 28, 2020
@mrBliss
Copy link
Contributor

mrBliss commented Nov 30, 2020

We have had another report of this on MacOS. I heard from someone that:

Apple don’t work hard to keep system time monotonic or accurate

Maybe there was a larger than usual system time adjustment recently?

In the Byron era with 20s slots, we could tolerate the system time moving up to 20s (exclusive) back, but now in the Shelley era with 1s slots, we only allow the time to move up to 1s (exclusive) back.

So the chances of seeing SystemClockMovedBack in the Shelley era are much larger. Because of this, we will do something about it: IntersectMBO/ouroboros-network#2781

@CarlosLopezDeLara
Copy link
Contributor

Fixed in IntersectMBO/ouroboros-network#2785

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

3 participants