Issue with workers not working after upgrading Airbyte version

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

Summary

Workers are not working after upgrading Airbyte from v0.53.0 to 0.62.4 on an EC2 Linux machine using Docker Compose. Error messages indicate a problem related to log4j.


Question

Hello guys,
I’m dying over here trying to find the issue thats happening for me but im not sure what to do. I was upgrading from v0.53.0 to 0.62.4.
I am running airbyte on an EC2 Linux machine, using docker compose.
My workers are completely not working, and i think there is a problem related to log4j. Any help please ?

....
2024-06-10T18:35:29.908502209Z pool-55-thread-1 ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.FileAppender for element File: java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.FileManager$FileManagerFactory@b834f0a] unable to create manager for [/tmp/workspace/2eac319a-2003-43a0-800d-59b4a2aebc6a/0/logs.log] with data [org.apache.logging.log4j.core.appender.FileManager$FactoryData@b21bbc8] java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.FileManager$FileManagerFactory@b834f0a] unable to create manager for [/tmp/workspace/2eac319a-2003-43a0-800d-59b4a2aebc6a/0/logs.log] with data [org.apache.logging.log4j.core.appender.FileManager$FactoryData@b21bbc8]
...
2024-06-10T18:35:29.908657589Z pool-55-thread-1 ERROR Unable to invoke factory method in class org.apache.logging.log4j.core.appender.FileAppender for element File: java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.FileAppender java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.FileAppender```

<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/p1718045163953009) if you want 
to access the original thread.

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

<sub>
["upgrade", "workers", "airbyte", "v0.53.0", "v0.62.4", "EC2", "linux", "docker-compose", "log4j", "error"]
</sub>
2

In the latest version of the docker-compose there is a breaking change related to the folder permissions needed.

https://airbytehq.slack.com/archives/C023W76QGE4/p1709744530251469

3

It is weird as the version you’re using is newer than the one this could be the problem

4

But that could you give some pointers :stuck_out_tongue:

5

Maybe because i originally upgraded from a lower version

6

that looks exactly like the issue

7

i just have one question please… if i remove this volume, will i lose all my data and configs ?

8

Check the docker-compose for the db service and what volume is mapping there. If it isn’t the same volume you won’t loose the data.

9

Thank you very much <@U01MMSDJGC9> :heart: I’ve been running out of hairs to pull due to this… thanks a million!!

10

it looks like my renaming went wrong :sweat_smile: i just dropped the workspace volume… and rebooted, its back to working fine :tada:
Thanks again a million and sorry for the disturbance :pray:

11

awesome! its not the same, i guess i’ll remove it so it would get recreated again

12

<@U01MMSDJGC9> I’m sorry to bother you, but I removed the workspace and even changed its name, however i can see its still attached to the root user inside the running container. is there something i’m missing ?