'SSL error: unsupported method about dbt-redshift

[jtcohen6]

@billy1s I'm not sure what's going on here. The codepath you're seeing is:

https://github.com/dbt-labs/dbt/blob/9e796671dd55d4781284d36c035d1db19641cd80/plugins/postgres/dbt/adapters/postgres/connections.py#L127-L135

This error message is coming straight from pycopg2, the library dbt uses to connect to Postgres + Redshift. I did some quick searching for psycopg2 ssl error unsupported method, but I didn't find any obvious leads. Without better visibility into the psycopg2 logs, it's hard to know what's going on here.

Until we have a better understanding of the underlying issue, or even what its error code is, I'm hesitant to consider it a transient error—that is, silently catch and retry—though that might be the ultimate resolution here (#3303).

Something we could consider doing is adding psycogp2 to the list of logger.getlogger().setLevel() calls here, so that you can show debug-level psycopg2 logs by setting an env var:

https://github.com/dbt-labs/dbt/blob/9e796671dd55d4781284d36c035d1db19641cd80/core/dbt/logger.py#L629-L642

(@kwigley @leahwicz An aside: We'll need to figure out how to lightly refactor this code post-#3361, so that the env vars + log level setting for adapter plugins does not happen inside core/dbt.logger.py.)

I do see that you're using dbt v0.16.1, which is fairly old. I don't think we've touched this code much in the past several releases, and every version of dbt-postgres from v0.16 to v0.20 has the same dependency requirement of psycopg2~=2.8. Still, it never hurts to try upgrading to a newer version.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.