Get Spec job failed for connector cloned in VM

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Debian
  • Memory / Disk: 4Gb
  • Deployment: Are you using Docker or Kubernetes deployment? Docker
  • Airbyte Version: What version are you using now? 0.40.26
  • Source name/version: ssp-xander-appnexus
  • Destination name/version: gcs
  • Step: The issue is happening during sync, creating the connection or a new source? - new source
  • Description: I have cloned airbyte repo in our debian vm in google cloud instead of installing it locally. The check/read operation works perfectly well as well as pushing the docker image into the google registry but the problem occurs when adding the connector to the UI.

I have followed all the solutions below which was discussed on this thread Internal Server Error: Get Spec job failed but it did not work for me.

Is this issue because of where I cloned airbyte? cloning airbyte locally is not an option for me and all dev work should be done in the google cloud vm.



ERROR in Adding the connector in UI

Suggested Solutions that I tried:

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