Crash loop when connecting to an external azure postgres db

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu and MacOS
  • Memory / Disk: 16Gb / Tb
  • Deployment: Docker
  • Airbyte Version: latest 0.40.23
  • Step: worker and cron containers crashes

hey,
I am facing an issue with aitbyte not starting when i connect it to an external db on azure postgress.

this is the logs i see in the worker container before it fails:

2022-12-22 14:33:21 INFO i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):221 - Waiting for temporal server...
2022-12-22 14:33:21 WARN i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):232 - Waiting for namespace default to be initialized in temporal...
2022-12-22 14:33:23 INFO i.t.s.WorkflowServiceStubsImpl(<init>):188 - Created GRPC client for channel: ManagedChannelOrphanWrapper{delegate=ManagedChannelImpl{logId=1, target=airbyte-temporal:7233}}
2022-12-22 14:33:30 INFO i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):249 - Temporal namespace default initialized!
2022-12-22 14:33:30 WARN i.a.m.l.MetricClientFactory(getMetricClient):46 - MetricClient has not been initialized. Must call MetricClientFactory.CreateMetricClient before using MetricClient. Using a dummy client for now. Ignore this if Airbyte is configured to not publish any metrics.
2022-12-22 14:33:30 ERROR i.m.r.Micronaut(handleStartupException):338 - Error starting Micronaut server: Error instantiating bean of type  [io.airbyte.db.check.DatabaseMigrationCheck]

Message: Version may only contain 0..9 and . (dot). Invalid version: 
Path Taken: new ApplicationInitializer() --> ApplicationInitializer.jobsDatabaseMigrationCheck --> DatabaseMigrationCheck.jobsDatabaseMigrationCheck(DSLContext dslContext,[Flyway jobsFlyway],String jobsDatabaseMinimumFlywayMigrationVersion,Long jobsDatabaseInitializationTimeoutMs)
io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.airbyte.db.check.DatabaseMigrationCheck]

Message: Version may only contain 0..9 and . (dot). Invalid version: 
Path Taken: new ApplicationInitializer() --> ApplicationInitializer.jobsDatabaseMigrationCheck --> DatabaseMigrationCheck.jobsDatabaseMigrationCheck(DSLContext dslContext,[Flyway jobsFlyway],String jobsDatabaseMinimumFlywayMigrationVersion,Long jobsDatabaseInitializationTimeoutMs)
        at io.micronaut.context.DefaultBeanContext.resolveByBeanFactory(DefaultBeanContext.java:2367) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2305) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2251) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.createRegistration(DefaultBeanContext.java:3016) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.SingletonScope.getOrCreate(SingletonScope.java:80) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.findOrCreateSingletonBeanRegistration(DefaultBeanContext.java:2918) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.resolveBeanRegistration(DefaultBeanContext.java:2879) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.resolveBeanRegistration(DefaultBeanContext.java:2800) ~[micronaut-inject-3.7.1.jar:3.7.1]
        at io.micronaut.context.DefaultBeanContext.getBean(DefaultBeanContext.java:1617) ~[micronaut-inject-3.7.1.jar:3.7.1]

i disabled firewalls and ssl for my db

my env for the db are

DATABASE_USER=aibyte
DATABASE_PASSWORD=pass
DATABASE_HOST=<my db name>.postgres.database.azure.com
DATABASE_PORT=5432
DATABASE_DB=airbyte_database
# translate manually DATABASE_URL=jdbc:postgresql://${DATABASE_HOST}:${DATABASE_PORT}/${DATABASE_DB} (do not include the username or password here)
DATABASE_URL=jdbc:postgresql://=<server name>.postgres.database.azure.com:5432/airbyte_database

the main DB gets initialized correctly and temporal DBs get created also

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hey, are you still experiencing this issue? Can you try the latest version of Airbyte and let me know if it’s the error continues?