Skip to content
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

Telegraf logs error about unable to create InfluxDB database #2739

Closed
phemmer opened this issue Apr 28, 2017 · 5 comments · Fixed by #2740
Closed

Telegraf logs error about unable to create InfluxDB database #2739

phemmer opened this issue Apr 28, 2017 · 5 comments · Fixed by #2740
Assignees
Milestone

Comments

@phemmer
Copy link
Contributor

phemmer commented Apr 28, 2017

Relevant telegraf.conf:

[[outputs.influxdb]]
  urls = ["http://influxdb.example.com:8086"]
  username = "telegraf"
  password = "secret"
  database = "telegraf"
  retention_policy = ""

System info:

Telegraf 1.3.0-rc1 + #2553

Steps to reproduce:

  1. Have an InfluxDB database where telegraf user is not an admin
  2. Start telegraf

Expected behavior:

No errors

Actual behavior:

telegraf[19617]: 2017-04-28T20:43:28Z E! Database creation failed: Response Error: Status Code [403], expected [200], [error authorizing query: telegraf not authorized to execute statement 'CREATE DATABASE telegraf', requires admin privilege]

Additional info:

Telegraf appears to function fine. Data is getting into InfluxDB, it just logs this error on start. Previous versions of telegraf did not do this.

@danielnelson
Copy link
Contributor

Maybe duplicate of #2496

@phemmer
Copy link
Contributor Author

phemmer commented Apr 28, 2017

It might be, though the description there indicates that writes don't even work. But it could be misreported.

@danielnelson
Copy link
Contributor

No it says writes are working:

I haven't found that further writes are broken if the database already exists despite the CREATE failure, but it does create a log entry each time Telegraf starts.

I think we should just silence this error for 1.3, assuming there is an error on write.

@phemmer
Copy link
Contributor Author

phemmer commented Apr 28, 2017

That comment wasn't from the author of the issue.

 

I think we should just silence this error for 1.3, assuming there is an error on write.

Sounds reasonable.

@danielnelson
Copy link
Contributor

Ahh, right.

The option suggested over there could be nice as it's own thing, so I'll keep both of these open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants