-
Notifications
You must be signed in to change notification settings - Fork 147
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
Unrecoverable Null Pointer Exception #118
Comments
Thanks for raising this Hayder. I've been at ETHDenver over the last few days, but will take a look ASAP. |
@craigwilliams84 I think also it would be a good idea to return a non-zero system code for something like this so kubernetes would automatically restart it. |
Hey @hshar7, this should be fixed on the development branch. It seems that infura have started sending null blocks every now and again, which Eventeum wasn't dealing with. |
Awesome -- Thanks! |
Hi team, Is there a fix for this issue? I'm getting the same issue as above when using wss on mainnet infura.
|
@grey007 Hey! The fix isn't on master until the next release (hopefully coming soon), so you have a couple of options: a) Use the development branch and/or latest docker SNAPSHOT. This is the latest unstable code so there are chances that the code may break. Also, there are also a number of other changes in this branch, especially around how events are monitored (via block inspection, rather than event filters). Cheers! |
Hey @craigwilliams84 I used the kauri0120 patch and it worked for most the day and now it's throwing a new error:
|
Hey! Could you post the full stack trace? The NodeHealthCheckService periodically polls the node (getting the latest block) to ensure the node is up and it seems that infura is responding with an invalid response. Does Eventeum ever recover from this point? |
Eventeum never recovers, unfortunately. Here is the full stack trace:
|
Here are the logs for when I restart the container:
|
@grey007 Hmmm, it seems that possibly the connection to the node is failing. You said that you're connecting to Infura right? Are you adding your api key to the infura node url? |
I am using infura, and I'm adding the API key + setting the block strategy to PUBSUB |
@craigwilliams84 I've seemed to get everything running again. The issue looks to be related to the events:
|
I am having the same issue , how can i solve this @craigwilliams84? |
Version: Building from master branch
Ethereum Node: Rinkeby WS Infura
Strategy: PUBSUB
Error:
The text was updated successfully, but these errors were encountered: