ot-node
ot-node copied to clipboard
3 Errors: ENOENT: no such file or directory, unlink // ArangoError: unique constraint violated - // ArangoError: precondition failed
Expected behavior
No error messages when running nodes
Actual behavior
Errors shown: Error: ENOENT: no such file or directory ArangoError: unique constraint violated ArangoError: precondition failed
Steps to reproduce the problem
This error occurs on any servers running nodes as confirmed by quite a few node runners.
Specifications
- Node version: 5.1.0
- Platform: Ubuntu 18.04 and 20.04
VPS specs : 8 vCPU Cores 30 GB RAM 800 GB SSD 3 Snapshots 600 Mbit/s Port 32 TB Traffic Unlimited Incoming
I get about: 2 to 4 times for ArangoError: precondition failed 30 to 60 times for Error: ENOENT: no such file or directory 10 to 20 times for ArangoError: precondition failed
The node keeps bidding and does not auto restart when these errors occur, I do see a lot of warn - MaxListenersExceededWarning: Possible EventEmitter memory leak detected (about 12 times in 24 hours)
Error logs
Error: ENOENT: no such file or directory, unlink '/ot-node/data/import_cache/0x9039c47b7b6be63aad7dc0497fe44f3d58157f61c3a0aa0928a7b23b0'
ArangoError: unique constraint violated - in index primary of type primary over '_key'; conflicting key: 0xd85050f76ed0a9a2bc5120eae3a62ae893490e31b2e73e734ce7af24ddb6a
ArangoError: precondition failed
warn - MaxListenersExceededWarning: Possible EventEmitter memory leak detected
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].
I got some screenshots from Telegram to hopefully help with this a bit more. You can see more of the logs for the errors reported originally.
1 ArangoError: unique constraint violated - in index primary of type primary over '_key'; conflicting key:
3 ArangoError: precondition failed
Research
The only theory I have is that data is being inserted twice (duplicates) into arango. precondition failed
seems to be according to arangodb source code related to conflicts with existing data. The same applies for the unique constraint violated error.
There's some limited data in Telegram that running multiple OTnode docker containers exhibit this problems. However, if you run multiple ot nodes without docker sharing the same arango server it does not exhibit these problems. The sample size for this limited data is 1 person but it's interesting to note.
Hi Tracers,
Thank you for submitting your detailed issue reports. We’re aware of the issue and are going to tackle it in the coming updates.
This issue is not relevant because it was for v5 and current version of OT-node is v6.