Airbyte 0.40.9 Worker failure: Failed to inject value for parameter [dslContext] of method [configDatabase] of class: io.airbyte.db.Database

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 100gb
  • Deployment: Docker
  • Airbyte Version: 0.40.9
  • Source name/version: NA
  • Destination name/version: NA
  • Step: The problem is at the initialization of the service
  • Description: I am following the GCP setup guides but after I run the docker-compose up step the process keeps failing because of the worker (airbyte-worker exited with code 1)

Additional details:

Caused by: io.micronaut.context.exceptions.NoSuchBeanException: No bean of type [org.jooq.DSLContext] exists for the given qualifier: @Named(‘config’). Make sure the bean is not disabled by bean requirements (enable trace logging for ‘io.micronaut.context.condition’ to check) and if the bean is enabled then ensure the class is declared a bean and annotation processing is enabled (for Java and Kotlin the ‘micronaut-inject-java’ dependency should be configured as an annotation processor).

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.
The Community Assistance Team

Thanks for raising the issue Mateo. I created the issue team is working on the solution.

Please upgrade to version 0.40.10 a fix was released for this issue in this version.

1 Like

just did that… working as expected! thanks