-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[0.9.2] panic: runtime error: invalid memory address or nil pointer dereference after start #3603
Comments
Thanks for the report @vovencij -- your trace implies a query was executing when this happened. Do you know what that query was? |
It is hard to tell with 100% confidence, but most probably, considering the logs of the client application, which reads and writes data to influx, it was a batch insert. |
Just a heads up i just upgraded and i am hitting this problem as well, is there any extra logging that i can turn on to help you guys troubleshot this? |
@timgriffiths - can you try a nightly build? We now handle an error that may have been causing this. Check the link below for nightly builds. |
@otoolep Can do, I will change it over at next crash otherwise after COB today |
So my problem still exists, i running the latest nightly build, below is the full error. it's weird it can run fine for hours with no one changing what they are running then it will crash
|
What are the details of your retention policies, please? |
Added this as part of working on issue #3603.
I took a look at the code, and have some ideas about what is going on, but am far from sure. Your system must be receiving queries during this time, as the code is crashing in the query engine. Are you running continuous queries? I am also wondering the data in the shards is getting deleted while the query is taking place. This shouldn't be an issue, but am considering it, hence my question regarding retention policies. |
In our case we have default retention policies (we do not specify any explicitly) and no continuous queries. |
so i have 5 databases, 4 of which have the
and the other is
|
@timgriffiths that last one is very confusing to me. It looks like you have a database that has no default retention policy. That shouldn't be possible. (There's an RP named "default", but the Can you run the |
Sorry that's a typo, you are correct all my databases have a default retention policy
|
Thanks, @timgriffiths. I discovered it is actually possible to end up in a state where there is no default retention policy (#3699) but I'm glad we can rule that out as a complicating factor in your issue. |
Hello, I ran into a similar error but not at starting time. Log is copied below:
|
Significant improvements to write path and speed in 0.9.3, released yesterday. I am provisionally closing this, please reply if you can reproduce the issue on 0.9.3. |
Hi, the orinigal panic mentioned in this ticket (invalid memory address or nil pointer dereference, /root/go/src/github.com/boltdb/bolt/db.go:422) is still occuring for me using 0.9.3. Not sure which query/write caused this exactly as we had modest production load on the db at that time. Gladly give a hint on how to make this more reproducable for you. Full stacktrace at: https://gist.github.com/consense/0b04ae6019ff37fbeb9c |
After getting timeouts and 500 errors on writes (no continuous queries) and restarting influxd 0.9.2 on Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-61-generic x86_64) it panicked and crashed. After next restart is started working again. Following is the log with the last events before restart and the crash log itself:
The text was updated successfully, but these errors were encountered: