https://linen.dev logo
Join Slack
Powered by
Hello everyone, with a colleague I try to get Air...
# replication-ask-ai
m
Hello everyone, with a colleague I try to get Airbyte up and running on an Ubuntu VM. We are able to install Docker and Airbyte and we also are able to use Docker Compose up. But when we check the tool on the browser, we get the error message: "Oops! Something went wrong… Cannot reach server. The server may still be starting up." When using docker ps I can see that the airbyte server and airbyte worker are restarting every few minutes. When checking the logs that docker prints to the terminal I can often see this message from server and worker: "airbyte waiting for namespace default to be initialized in temporal" Temperoal is permanently stuck in a loop of restarting. I checked this with docker ps too. Using Google I found a lot of calls for help about the same problem. However, I didn't find a recommendation about what to do to fix this problem. Last weekend I successfully deployed Airbyte on a private EC2 instance also running Ubuntu. And I can also run Airbyte locally with Docker Desktop. I suspect that either the Ubuntu version we run at the company or some other setting we use is making the difference. Do you have recommendations about where I should start looking for the error? Or has someone solved it in the past and can tell me what to do? Looking forward to your help 😇
k
Based on the information provided in the extracts, it seems like you're encountering a common issue where the Airbyte server is unable to start up properly. This could be due to a variety of reasons, including issues with Docker, the specific version of Ubuntu you're using, or other system settings. Here are a few things you could try based on the information from the extracts: 1. Check Docker Version: In one of the [forum discussions](https://discuss.airbyte.io/t/3583), a user had a similar issue and found that the problem was caused by the snap version of Docker. They resolved the issue by completely removing the snap version and installing the apt version of Docker. Ubuntu seems to always prefer the snap version, no matter what other Docker versions are installed. 2. Check Airbyte Version: In another [forum discussion](https://discuss.airbyte.io/t/3943), a user was unable to run Airbyte locally due to an issue with the Airbyte version. They resolved the issue by cleaning their Docker images and starting over. 3. Check System Resources: Make sure your Ubuntu VM has enough resources (memory, disk space, etc.) to run Airbyte and all its components. In one of the [forum discussions](https://discuss.airbyte.io/t/2305), a user was unable to start PostgreSQL (which is a component of Airbyte) due to insufficient system resources. If none of these suggestions work, you might want to reach out to the Airbyte community on their [forum](https://discuss.airbyte.io) or [Slack channel](https://airbytehq.slack.com) for more specific help.
I'm sorry, but I am only able to provide information based on the extracts provided from Airbyte's documentation, tutorials, YouTube videos, forum support questions, and past support answers from Slack. The link you provided is not listed in the information extracts. If you have any questions about Airbyte, feel free to ask!
m
@kapa.ai which version did the user from your second point use in the end?
k
A message from kapa.ai
The user in the second extract ended up using Airbyte version 
0.40.30
. However, they faced an issue as there was no helm chart available for this version. The helm chart jumped from 
0.40.29
to 
0.40.32
. The support suggested using 
0.40.29
instead. Here is the relevant extract for your reference:
Copy code
User: Hello Layth, version 0.40.32 and 0.40.31 have bugs. Please downgrade to 0.40.30 check release notes here: <https://github.com/airbytehq/airbyte/releases>  User: Unfortunately there is no helm chart for 0.40.30. it jump from 0.40.29 to 0.40.32 ```airbyte-oss/airbyte            0.44.1        0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.44.0        0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.36       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.34       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.33       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.32       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.31       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.30       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.29       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.28       0.40.32     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.24       0.40.29     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.22       0.40.29     Helm chart to deploy airbyte            airbyte-oss/airbyte            0.43.21       0.40.29     Helm chart to deploy airbyte
Support: Well… in this case better to use 0.40.29 🙂 ```
m
@kapa.ai What is the current version of Airbyte? In my docker compose file it says I currently use version 3.8 in the beginning. Is this the current Airbyte version?
k
A message from kapa.ai
The version 
3.8
you're seeing at the beginning of your Docker Compose file is likely the version of the Docker Compose file format, not the version of Airbyte. Based on the information provided in the extracts, the latest version of Airbyte mentioned is 
0.44.0
in the context of Airbyte Open Source running a security self-check during setup. However, please note that this information might be outdated as Airbyte is rapidly evolving. For the most accurate and up-to-date information, you should check the [official Airbyte releases page on GitHub](https://github.com/airbytehq/airbyte/releases).
m
@kapa.ai How can I check the airbyte version I currently run?
k
A message from kapa.ai
The version of Airbyte you're running is defined in your 
.env
file. You can check this by opening the 
.env
file in the root directory of your Airbyte installation and looking for the 
VERSION
variable. Here's an example of what you might see:
Copy code
VERSION=0.44.0
In this example, 
0.44.0
is the version of Airbyte that's currently running. Please replace 
0.44.0
with your actual version number. If you're running Airbyte on Kubernetes, you might need to check the version in a different way, depending on your setup. For more detailed instructions, you can refer to the [official Airbyte documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte).
m
@kapa.ai At what path is the .env file usually installed when using ubuntu?
k
A message from kapa.ai
The 
.env
file is typically located in the root directory of your Airbyte installation. If you installed Airbyte in a specific directory, you should find the 
.env
file there. For example, if you cloned the Airbyte repository into a directory called 
airbyte
in your home directory, the 
.env
file would be located at 
~/airbyte/.env
. Please note that the location of the 
.env
file can vary depending on where and how you installed Airbyte. If you can't find the 
.env
file, it's possible that you might have installed Airbyte in a different directory.
m
@kapa.ai where does 
docker rm $(docker ps -a -q)
install datahub?
k
A message from kapa.ai
@Merlin Nestler That's a great question, but unfortunately I am only capable of responding to a maximum of five questions per thread. Don't hesitate to create a new thread for any further questions you have though. I'm here to help!
d
I think you can refer to my message to fix your problem @Merlin Nestler https://airbytehq.slack.com/archives/C01AHCD885S/p1690197999580929
m
@Dave Thanks a lot. Your fix worked 👍
👍 1
2 Views
Open in Slack
PreviousNext
Powered by