-
Notifications
You must be signed in to change notification settings - Fork 795
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: Error running node agent tick #3952
Comments
Several other people also got this error, including me. So the bug is present on windows, linux and iOS. |
Same error here too Any info? |
Same here too |
@mumoshu could you take a look? |
Potentially related to #3906 |
We appreciate your reporting this issue to us! In short, this isn't an error by itself. We need to make it flow into a lower log level, like debug, trace, or something like that. FWIW, SurrealDB has an internal mapping between timestamps(ts) and commit versions(we call it "vs" and "versionstamp"). You can treat it as follows:
@admtech @vitorTheDev The "ERROR" (although it isn't a fundamental error as written earlier) means that 3. failed temporarily for various reasons. It can happen when your operating system corrected the host's clock using NTP after the previous run of 3. succeeded, or you have multiple SurrealDB nodes connected to a single distributed KVS(TiKV, for example), and there are skews across nodes' clocks... SurrealDB handles those "errors" gracefully so that any system clock skews don't break the correctness of CF or other SDB functionalities.
@kirinse In addition to the above, this error on the All in all, this is fine. We need to make it flow into a lower log level, like debug, trace, or something like that, so that they don't confuse you anymore. |
We started SurrealDB with:
surreal start --log info --bind 0.0.0.0:8000 file:///opt/surrealdb/data/
After a while the message appears:
ERROR surrealdb::api::engine::tasks: Error running node agent tick:...
However, the server remains functional and does not crash.
Greetings
Frank
SurrealDB version
Running 1.4.2 for linux on x86_64 (Ubuntu LTS)
The text was updated successfully, but these errors were encountered: