Is this your first time deploying Airbyte: No OS Version / Instance: Mac OS Ventura (M1 Apple Chip) Memory / Disk: 16Gb / 1Tb SSD Deployment: Docker Airbyte Version: 0.40.22 Step: Deploy on local (Docker compose up) Description: I'm trying to deploy airbyte open source on mi laptop using docker. but at some point docker compose up started to show this error. airbyte-webapp | 2022/11/23 234644 [error] 35#35: *16 connect() failed (111: Connection refused) while connecting to upstream, client: 172.21.0.9, server: localhost, request: "POST /api/v1/workspaces/list HTTP/1.0", upstream: "http://172.21.0.7:8001/api/v1/workspaces/list", host: "localhost", referrer: "http://localhost:8000/" I try to used all the options that mention in comments related even with the M1 Apple chip. The bootloader container exited with this 2022-11-23 234551 WARN c.z.h.p.HikariPool(shutdown):218 - Timed-out waiting for add connection executor to shutdown (edita (editado)

Hi, Juan! Could you brainstorm with me on what might have caused this? Did you update or change something in your configuration? This setup looks very straightforward, I don't see errors like this too often.

I run once an it was working. Then I uninstall anaconda distribution and I updated my Mac from Monterrey to Ventura. Then I wasn't enable to run airbyte again in my local. I reset. to factory my laptop trying to resolve the problem but that's not work. Even I tried reinstalling docker. I have another to team members that have the same laptop and they can run airbyte locally.

Huh! I know we've got engineers who have updated and everything works, so I'd say it's probably not the Ventura update. Do you know if your Python version could have gotten updated?

I'm using pyenv set with 3.9.11 python version. but know already I installed anaconda trying to fix the airbyte.

Would you be able to provide the full logs? I wonder what else is in the stack trace that could be helpful to figure this out!

Thanks for you support! 🙏

Hello Juan Chaves, it's been a while without an update from us. Are you still having problems or did you find a solution?

Hey Juan, following up on your other post in this thread. You might need to add more resources to your deployment. Please check out the Scaling Airbyte doc and let us know if it helps

Hey Sunny, already I added more resources to my docker ( CPUs:6, Memory:16GB, Swap: 4GB, Virtual disk limit: 64 GB) but that's not worked

Hi Juan, thank you so much for your patience on this! Did you upgrade Airbyte right before this started happening? I saw a similar issue from a user that was upgrading from an older version. As a nuclear option I'd suggest doing a fresh install, but that's as a last resort!

Hi Nataly, I'm using the repo for the airbyte open source and I execute the docker compose up command. So what you mean with updgrade? Get the last version of the repo? What you mean with fresh install? I reset my laptop to the initial state trying to solving the problem, even I reinstalled the docker desktop. Could you give me more detail explanation and step by step to solve it please, thanks!

By upgrade I meant that you were on one version of Airbyte and upgraded it to a newer version. By a fresh install I meant deleting the local Airbyte repository, recloning it from GitHub and installing everything fresh. 1.

sudo rm -rf airbyte

if everything is in a folder called

airbyte

2. Git clone the repo again 3.

docker compose up

@Nataly Merezhuk (Airbyte) this issue also happen with me multiple time when we call api

/api/v1/jobs/list

multiple time parallel(promise.all) immediatly after this sever hangs after it recovers i could see more than under logs of below message

2023/01/18 13:12:14 [error] 30#30: *3998 connect() failed (111: Connection refused) while connecting to upstream, client: 10.2.13.199, server: localhost, request: "POST /api/v1/jobs/list? HTTP/1.1", upstream: "<http://172.18.0.2:8001/api/v1/jobs/list>", host: "10.2.11.63:8000

@Akilesh V could you please open an issue on GitHub? Thanks!