[2.x] 2.7.4: panic: runtime error: invalid memory address or nil pointer dereference #24536
Comments
andig
changed the title
|
Note: panic seems to occur when when empty Tags are included in the query (notice right column): 
It's unclear where those tags come from. |
|
I encountered the same problem because there are multiple types of the same field in the measurement. After clearing the data in the measurement, it returned to normal. Of course, I need to ensure programmatically that when writing data to Influxdb, the data type of the same field remains unchanged.
you can use this command to test whether or not have the same problem. see: #8085 |
philjb
changed the title
|
@shengbinxu I might have the same problem. Can you (or someone else) elaborate on the test Because my database is not configured for InfluxQL, I tried to use |
You mean you can't use InfluxQL? 
|
|
@shengbinxu thanks for the clarification! I indeed didn't need special configuration ("DBRP mappings", that was confusing me). I did have to add the database name (i.e. bucket name) to the query, and I changed the query to inspect all measurements, since I don't have that many:
This showed a problem in the database:
So it seems data was written to the database, while it should have been rejected because it had the wrong type. I also have a stacktrace, which I hope is helpful in fixing the bug. To me it looks similar to the stacktrace of @andig, but with |
InfluxDB does allow writing different types of values to the same field, which can be confusing. However, it is true that I have successfully written different types of values to the same field in my business. Can you control your business code to ensure that only the same type of value can be written to the same field? |
That's something I wasn't aware of! When I was experimenting with InfluxDB I saw error messages like We will fix our business code so that the right data type is sent to InfluxDB. Nevertheless: writing data should never make existing queries end in a panic runtime error. I hope the developers are able to resolve this issue in a future release. |
Do not panic if a cursor array is nil and the number of timestamps is retrieved. closes #24536
Do not panic if a cursor array is nil and the number of timestamps is retrieved. closes #24536
Steps to reproduce:
Use data explorer to browser measurements and tags, finally click "Submit"
Expected behaviour:
No panic
Actual behaviour:
Panic:
Environment info:
RUSTFLAGS.uname -srmor similar and copy the output here (we want to know your OS, architecture etc).Config:
Copy any non-default config values here or attach the full config as a gist or file.
Logs:
Readable version:
The text was updated successfully, but these errors were encountered: