Error syncing Fields for Table

Hi,

I connected a Postgres database via a SSH tunnel.
The connection works fine.
But when I try to sync the database here is the log I receive:

[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:01:24-07:00 INFO metabase.sync.util STARTING: step 'sync-fields' for postgres Database 5 'demographic - staging'
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:01:34-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 311 'public.user_invoice''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:01:44-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 310 'public.user_submission_form_values_student_college_selection''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:01:54-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 309 'public.user_student_info''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:02:04-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 308 'public.user_self''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:02:14-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 307 'public.user_student_info_confirmed_aids''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:02:24-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 306 'public.user_student_info_invoiced_products''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:02:34-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 305 'public.user_submission''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:02:44-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 304 'public.user_submission_form_confirmed_aids''
[65b563e2-f72e-40f7-8e65-9f3cb88178ab] 2020-04-15T11:02:54-07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 303 'public.user_student_info_values_student_college_selection''

Which leads to the following when I try to explore the DB:

Distinct, non-empty sequence of Field clauses

Would love to have your insight!

Thanks!

Hi @zigzhang
That’s a known issue:
https://github.com/metabase/metabase/issues/8396 - upvote by clicking :+1: on the first post
The workaround is to setup the SSH tunnel yourself instead of using the one built-in to Metabase.

Thanks for the reply @flamber!
I upvoted the issue, and will look into setting up the SSH tunnel myself.
Do you happen to have any known guide to do that on Elastic Beanstalk?

@zigzhang Uhhh, I think you’re fairly limited on EBS and Heroku, so I don’t think you’re able to access the console to setup tunnels manually. If you find a way around it, then please post a comment - it would be good to know.

@flamber thanks for your reply!
I did a workaround - in case it’s interesting for someone, leaving the high level idea here:
My issue was that I had my RDS in a VPC, and Elastic Beanstalk in another VPC.
I did a VPC Peering Connection between the two, and was able to connect directly without SSH Tunnel.

1 Like