-
Notifications
You must be signed in to change notification settings - Fork 156
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
Random "DB lookup fail in insertABlock" error #304
Comments
I have seen
before, but one was due to postgres running out of disk space and the others were after I did potentially unsafe manipulations of the database during testing. As for the My suggestion is :
|
Sorry, I forgot to mention that it did not happen anymore since that time from the attached logs; that's why I assumed it could have been some exceptional problem with my |
We can keep this open for a while to see if we come up with any more helpful clues. |
JFTR, I'm resyncing mainnet from the scratch and found that it actually recovers after a big while (at least on latest version) and that it's probably caused by some [0]
|
That by itself would not cause a DB lookup fail. However, if You will notice that when the socket returns, it rolls back to block hash |
Is it worth keeping this open? The problem is that in almost all cases, I cannot fix problems I cannot reproduce. |
As per requested by @erikd on this other issue, I'm reopening this as a fresh issue since I got hit by this in the latest
5.0.1
version packaged in the officialhub.docker.com
image (inputoutput/cardano-db-sync:5.0.1
[0]).I must say problem has not reappeared again since the crash from these logs [1][2].
I think it might be caused by some
postgresql
connectivity problem, but anyways, IMHO, in worst case main process shouldexit >0
(as it doesn't recover from the db thread shutdown automatically) or db thread should be restarted when these exceptions are raised.[0]
inputoutput/cardano-db-sync@sha256:b09f440d868749135e74c0bfe6154f210d5836bc2d24a44e484c7dbb4b837689
[1]
[2]
The text was updated successfully, but these errors were encountered: