You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
Describe what you expected to happen.
Some sort of detailed error message Actual behavior:
Describe What actually happened.
"An internal error has occured"
Environment info:
System info: Run uname -srm and copy the output here
InfluxDB version: Run influxd version and copy the output here
Other relevant environment details: Container runtime, disk info, etc
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Logs:
Include snippet of errors in log.
Performance:
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.
# Commands should be run when the bug is actively happening.# Note: This command will run for at least 30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"
curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz`, `vars.txt`, and `iostat.txt` output files.
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
curl --data '{"MYSQL_USER", "davidgs"}' --request PATCH --url https://us-west-2-1.aws.cloud2.influxdata.com/api/v2/orgs/f978dfb87de31ea3/secrets --header 'Authorization: Token token>'
Expected behavior:
Describe what you expected to happen.
Some sort of detailed error message
Actual behavior:
Describe What actually happened.
"An internal error has occured"
Environment info:
uname -srm
and copy the output hereinfluxd version
and copy the output hereConfig:
Copy any non-default config values here or attach the full config as a gist or file.
Logs:
Include snippet of errors in log.
Performance:
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.
The text was updated successfully, but these errors were encountered: