-
Notifications
You must be signed in to change notification settings - Fork 5.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
postgresql_extensible.query cannot connect to pgbouncer #3253
Comments
Is this from the Open call here? https://github.com/influxdata/telegraf/blob/master/plugins/inputs/postgresql_extensible/postgresql_extensible.go#L134 |
did we actually confirm it worked? the pgbouncer PR had mixed statements from others on it working? I don't remember the failures being understood and addressed. the error mentioned here is a protocol violation. Also looking at your configuration: its going to default to port 5432.... is pgbouncer running on that port? Also what is your pgbouncer configuration? |
@danielnelson I can't say @james-lawrence nope nobody confirmed, and you're right according to #2573 (comment), it was not working. pgbouncer is listening on 5432 port and pooling connections from localhost application to a remote database pgbouncer is listening on 5432 port
Here is my pgbouncer config
|
k, I might have a chance to look into this. but will depend on my mood. =) |
@mced, alright did some investigation,
|
Tank you for your feedback. |
99-pgbouncer.conf.zip @james-lawrence On my scenario it's the last one:
Both telegraf input plugin and pgbouncer config files are attached. IPs and passwords have obviously been redacted.
|
@rsaffi thanks for the information. I got buyin from the pgx maintainer to make the implicit prepared queries optional. so fixing the issue will be pretty straight forward just need to find the time to do it. |
I just ran into this issue today, is there a workaround for collecting
Thanks, and sorry for highlighting the issue without a constructive contribution. |
@leehambley Well, I ended up making a python script that does the trick. I am using it with the "exec" plugin from Telegraf to send metrics to InfluxDB and it has been working great so far. https://github.com/CrossEngage/telebouncer PS: In case it's not allowed to crosspost to another project like I did, please accept my appologies and feel free to remove this comment! |
@leehambley there isn't currently a work around. its just straight up work that needs to be done in the driver we're using. |
Thanks, actually took the chance to remove PGbouncer from the stack, a 🎉 🎈 followed :) 👍 |
@james-lawrence if use pgpool not pgbouncer,your pr seems can't resolve the "show ..." query return err. # |
driver can now support will need a separate plugin that overrides the DB creation and use the below for the driver:
so if someone wants to pick up the work its doable now. |
. E
czw., 2 sie 2018, 00:44 użytkownik Greg <[email protected]> napisał:
… Closed #3253 <#3253> via
#3918 <#3918>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3253 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AChkHrK-9xzJlvYV3g5srZrcBiNWbTjrks5uMi9FgaJpZM4PdrCI>
.
|
I've got this with pgbouncer input after upgrading to Telegraf 1.9.4
On 1.9.0 there were no errors. Config is the same. |
@urusha I don't believe anything has changed in this plugin, can you try to isolate the first Telegraf version where this error occurs and then open a new issue? |
@danielnelson The version is 1.9.1. Please, see #5455 |
Bug report
With last version 1.4, many of us thought that telegraf was compatible with pgbouncer through postgresql_extensible.query input plugin.
It is not the case.
Relevant telegraf.conf:
System info:
Telegraf v1.4.0 (git: release-1.4 34b7a4c)
Ubuntu 14.04
pgbouncer 1.5.4
Steps to reproduce:
Add telegraf user in pgbouncer config file as
admin_users
.Then run telegraf.
Expected behavior:
Actual behavior:
The text was updated successfully, but these errors were encountered: