New user. Signed up to use free account, sent a few MB of data.
The cloud v2 ui is really buggy: feels like half the time it just says "failed to initialize execute state: could not find bucket ". I click around a bit, and things mysteriously start working for a bit, before reverting.
Am I doing something wrong? Is this typical on the free account, like caused by a throttle or something? The first impression it gives is not great
I tried from Safari and Google Chrome, from multiple computers (all Macs, but hey). Same everywhere. Also I searched the documentation and forums - nothing else mentions the same error message
And hereâs the (crazy!) behaviour I get when logging out/in. I resorted to a private browser window and logged in. Mystery bucket behaviour still happening afterwards: Tapes for Mac â Share Screencasts Fast
I just signed up for InfluxDB Cloud 2 on Azure, free account, and I am seeing this error most of the times while trying to query any data. I didnât see any data being reverted though.
Hi, I found out that in Influxdb 2.0.4, just released Feb 4 as GA, that I cannot restore (a backup created with "influx backup) to an existing bucket. Tried all combinations. So I added a delete bucket to the script and then restored to the bucket I wanted, using this: âinflux restore -c default -o commscope --bucket telemetry --new-bucket telemetry --new-org commscope --input /tmp/backupTelemetry /tmp/backupTelemetryâ and that âworksâ however, when I log back into the container (this is a v2.0.4 docker inside a kubernetes pod) and try to query from the bucket, using: influx query âfrom(bucket:âtelemetryâ) |> range(start: -15d)â it returns this: Error: Failed to initialize execute state: could not find bucket âtelemetryâ.
See âinflux query -hâ for help But the bucket is there:
but the bucket is there; # influx bucket list -c default
ID Name Retention Organization ID
db75828123589748 _monitoring 168h0m0s 9880bacb06b676ee
3dd3394c6332ca7a _tasks 72h0m0s 9880bacb06b676ee
96301b50be7cb690 alarms 720h0m0s 9880bacb06b676ee
5d5bb0fae5ea9e4c telemetry 720h0m0s 9880bacb06b676ee
Iâm surprised about not being able to restore to an existing bucket, as it creates a bunch of work if deleting it in order to restore, as then I have to redo user auths that were associated with the bucket since the bucket will change ID. However, that aside, Iâm currently stuck. This is a show stopper for us in regard to using 2.0.4. My restore script also restored the alarms bucket, after dropping it in order to restore and it is in the same situation:
influx query âfrom(bucket:âalarmsâ) |> range(start: -15d)â
Error: Failed to initialize execute state: could not find bucket âalarmsâ.
See âinflux query -hâ for help
BTW, in regard to the âError: Failed to initialize execute state: could not find bucket âtelemetryâ.â After dropping the bucket in order to restore it, one needs to remove the auth for users accessing such bucket(s) and rebuild the auth granting privileges on the new buckets (ID changes, not surprisingly with bucket remove/re-create). Using the admin token also works, I didnât add any â-c defaultâ to the end of the query, which does the trick. Iâll have to add the auth removal, config using that auth removal, create new auth for the changed bucket IDs and create a new config based on that new auth. A lot more work than it would be to simply be able to restore to an existing bucket (btw, I tried with -f and --force (thinking maybe they just werenât documented, but neither worked).