Wrong error message when executing a SELECT query.

[christophmerscher]

Hi everyone,

I'm trying to run a simple SELECT query from my database but it fails with following error message:

influxdb.exceptions.InfluxDBClientError: 403: {"error":"error authorizing query: my_user not authorized to execute statement 'SELECT * FROM \"measurements\"', requires READ on True"}

I know that my user have the required permissions because when connecting to the DB with a CLI I can execute the query. On top of that I checked the permissions with SHOW GRANTS and I could see that all requirements are satisfied (the user actualy does have all privileges).

I saw some simillar issues already (for instance in this issue) however this does not fit my case since I'm quoting the query.

My code:

results = influx_db_client.query('SELECT * FROM "measurements"')

What looks weird to me is that in the error message the qutoes around table are escaped.

• InfluxDB version: 1.8.0
• InfluxDB-python version: 5.3.1
• Python version: 3.6.8
• Operating system version: CentOS 7

[christophmerscher]

Anyone else facing this issue ?

[babaMar]

Anyone else facing this issue ?

I am facing exactly the same issue. And it works with same user/pass from CLI

[christophmerscher]

Hi @babaMar,

I wasn't able to solve the issue. However, when I wrote the code in Java I was able to run my query. Hence, I had the assumption that their might be an issue with the python API of influxdb.

If you can use a different language I would recommend to do so (Cause as mentioned for me when swtiching to Java it worked straight ahead).

However, I'm still curious to find out the actual cause of the issue.

[babaMar]

Hi @babaMar,

I wasn't able to solve the issue. However, when I wrote the code in Java I was able to run my query. Hence, I had the assumption that their might be an issue with the python API of influxdb.

If you can use a different language I would recommend to do so (Cause as mentioned for me when swtiching to Java it worked straight ahead).

However, I'm still curious to find out the actual cause of the issue.

I think I found the problem on my side. Most likely you're passing something else instead of the DB, and even if it doesn't exist it raises that error. requires READ on True it seems your client has True as DB

[christophmerscher]

Too bad that I do not have the code base anymopre but good to know that the issues wasn't on the API but in my code base. Thx for the update