-
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
[10.3] runtime error: slice bounds out of range => data corrupted #6054
Comments
@max3163 Could you describe what kind of data you were writing in to the database? Did the server crash while running, or was after a clean shutdown and restart? Is this reproducible? What library/script are you using to populate the database? How many measurements/series were you creating? How many fields and of what types were you creating for each series? Would you be able to upload/share an archive of your influxdb directory? This appears to be the same error in #6022, but we haven't gotten any further detail from that issue. Any information you can provide to help us diagnose or reproduce this would be very helpful and appreciated. |
Hi, Assuming the crash come from the rp : one_week ( like I could see in the log ) I wrote only log data ( so string data ) in this database. The server crash while running. And after a restart, the server crash too, when the corrupted data loaded. I can't reproduce it. I think it's possible that a special caractere was sent and crash / corrupt the database but I can't know which one. I don't have saved the corrupted data file so I can't upload/share the archive to you... Hope I've helped you. |
Thank you for providing what information you could. I'll continue to track this via #6022 |
Hi,
This afternoon, ur influxdb database ceased operating with this error :
panic: runtime error: slice bounds out of range
Impossible to restart the application, when the corrupted data loaded, influxdb crash again.
The only solution, delete in data and wall directory the corresponding file....
The text was updated successfully, but these errors were encountered: