nil pointer exception on v7.0.1-beta #613
Labels
bug
Something isn't working
Comments
|
If it helps at all its a pi4 node built with node:11 (latest?) and golang/v1.13.4 and I can answer any other question or try anything. |
|
@jacobrosenthal we don't currently test Mesh with Go 1.13 and we know that there are some issues with it. See #480. Can you try Go 1.12? |
|
sure
…On Tue, Dec 31, 2019 at 1:32 PM Alex Browne ***@***.***> wrote:
@jacobrosenthal <https://github.com/jacobrosenthal> we don't currently
test Mesh with Go 1.13 and we know that there are some issues with it. See
#480 <#480>. Can you try Go
1.12?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#613?email_source=notifications&email_token=AADPI5AUARTKE7FSY3EYNLTQ3OT4FA5CNFSM4J7RWVHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4U56I#issuecomment-569986809>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADPI5GWV7SRJEYQRAZUWVTQ3OT4FANCNFSM4J7RWVHA>
.
|
|
I think this was an arch issue with docker and pi. Either way by cleaning up my dockerfile because of the new go modules development branch, I havent seen it again. Please close. |
|
Nevermind. Found it in logs again today. |
|
Possibly related, I have all this in the logs a few min before |
|
@jacobrosenthal can you please provide steps to reproduce? The |
|
Im running a docker container on a platform called balena. My Dockerfile is
here
https://github.com/jacobrosenthal/balena-crypto-nodes/tree/master/balena-0x_mesh
…On Tue, Jan 7, 2020 at 6:33 PM Alex Browne ***@***.***> wrote:
@jacobrosenthal <https://github.com/jacobrosenthal> can you please
provide steps to reproduce?
The cannot perform more than one operation (insert/delete/update) on the
same model within a transaction error is not related. That is a separate
bug which we are working on fixing. See #608
<#608>, #614
<#614>, and #623
<#623>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#613?email_source=notifications&email_token=AADPI5AOSB3YMAVDDC4OPGDQ4UUQJA5CNFSM4J7RWVHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIK4JYY#issuecomment-571852003>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADPI5GCJMHEKAVHATE6GPTQ4UUQJANCNFSM4J7RWVHA>
.
|
|
Note this is reoccurring with no client connecting. so its not related to client code requests. |
|
@jacobrosenthal so to be clear, this happens whenever you run the docker container? Are you doing anything else to trigger it? Does it happen every time? |
|
Yeah after some amount of time running, not immediately. Yeah eventually it kills itself, gets restarted, and then works seemingly flawlessy again for half hour or hour or something I think. |
|
@jacobrosenthal we fixed a bunch of nil pointer exceptions in the latest version of Mesh ( |
|
I tried v8.2.0 today, still there |
|
@jacobrosenthal can you share the entire stack trace? Is there anything before Noe one else has reported an issue exactly like this so I'm starting to think it might be a problem with your platform/setup. |
|
Im up to v9.0.0, golang:1.13.4, Still there. Message looks same as all other versions Not sure how to give you more from golang. Happy to run with some debug environment variable or something if you can point me to it. |
|
9.1.2, golang:1.13.4, Still there. . Previously I could use it for.. 30m or hour or something and just reconnect the order watcher. Now I cant receive a single order, connecting to the node seemingly crashes and restarts immediately now. |
|
@jacobrosenthal here are some things you can try:
If neither of those fixes the issue, I'm fairly certain the problem lies with your platform and not with Mesh. Have you tried opening an issue for balena? |
|
Closing this issue because there has not been any activity for a while. @jacobrosenthal let us know if we're missing something and we can potentially re-open the issue. At this point, Mesh is fairly stable in production and I have not seen anyone else report an issue like this. I think we have to assume it is an issue that is specific to either the Raspberry Pi or Balena. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A user reported this on Discord:
At first glance, I cannot see how this could happen in
trackingRateLimiter.resetViolations. Need to investigate further.The text was updated successfully, but these errors were encountered: