Error after upgrading Airbyte to version 0.55.1 on Linux Ubuntu for all connections

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

After upgrading Airbyte to version 0.55.1 on Linux Ubuntu, users are encountering a configuration check failure with an internal error related to the scheduler used by Airbyte.


Question

Hey Guys,
I have airbyte deployed on linux ubuntu and I get following error after upgrading to 0.55.1 for all connections

The check connection failed because of an internal error
Internal message: The check connection failed because of an internal error in the scheduler used by airbyte.
Failure origin: destination```

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1711356903827139) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["error", "upgrading", "airbyte", "0.55.1", "linux-ubuntu", "configuration-check", "internal-error", "scheduler", "connections"]
</sub>
2

<@U04A692M4RE> How did you downgrade? I’m now running into the same issue

3

<@U06PWCLD0CE> just type the version number into the field where the current version is displayed and click upgrade. Is a bit counterintuitive but works

4

<@U04A692M4RE> Thanks for posting about this. I am seeing the same issue after upgrading a Docker installation running on EC2. Are you still running an older version and which version did you roll back to to resolve this?

5

<@U031QAT962C> still running at 0.50.54

To scared to upgrade atm

6

<@U04A692M4RE> I was able to resolve this with help from <@U02TNBMDUMQ>. The <March 2024 | Airbyte Documentation release notes> for March mentioned a breaking change for Docker deployments and there is some additional detail. In my case, I was able to resolve the https://github.com/airbytehq/airbyte/discussions/36984|issue without stopping the deployment or deleting the volume with the following commands, run from the host machine:

chown -R airbyte:airbyte /tmp```
Thanks to <@U02TNBMDUMQ> for the explanation and addition to the docs and to <@U02TQLBLDU4> for pointing me to the draft release notes that connected me with the answer.
7

seems to have worked. Thank you <@U031QAT962C> for updating!

8

Thanks <@U031QAT962C>!!

9

Me too! Running into the same error after upgrading to 0.55.1 and 0.55.2 on Ubuntu. In addition to the configuration check failure, I’m getting a “Get Spec Job Failed” error when trying to load custom sources. The same custom source functioned perfectly prior to the upgrade on version 0.52.

10

I downgraded my version to 0.50.54, everything is working again <@U05NC2U50KH>

11

> Thanks for the tip, <@U04A692M4RE>! Downgrading seems to be a temporary http://fix.In|fix.In the meantime, are there any known workarounds or alternative solutions we could try while waiting for the next release?

12

<@U05NC2U50KH>
I did a bit of digging in the docker logs of the airbyte worker

Here is what I found:

java.io.IOException: Could not create directory /tmp/workspace/7431a72e-b841-7ec6-94d9-d9ed39b44a16/0
ERROR StatusConsoleListener Unable to invoke factory method in class org.apache.logging.log4j.core.appender.FileAppender for element File: 

ERROR StatusConsoleListener FileManager ```
It seems like airbyte isn't able to create the folder but I couldn't figure out why
13

> Thanks for digging into the logs, <@U04A692M4RE>! The java.io.IOException: Could not create directory error definitely points towards a permission issue.
> I also encountered the same error message, and even running Airbyte with superuser permissions didn’t resolve it.