airbyte-cron and air byte-worker loop upon installation

[MFIHRI]

Running either docker-compose up or ./run-ab-platform.sh gives me hours long loop:

Airbyte Version: v0.50.19.
Docker-version(Windows 10): 24.0.5, build ced0996
Docker-version(Mac): 20.10.8, build 3967b7d

Running either docker-compose up or ./run-ab-platform.sh gives me hours long loop affecting airbyte-cron and airbyte-worker.

Errors I noticed in the Windows log Windows-10_Installation-log.docx :

1. main ERROR Error processing element Log4j2Appender ([Route: null]): CLASS_NOT_FOUND (see line 1308 on Windows log)

Stackflow has a mention of that error:

https://stackoverflow.com/questions/36978115/log4j2-error-processing-element-appender

2. • Could not find airbyte.yml file (see line 1457 in Windows log - error repeats downwards)

3. "Debug" loop affecting airbyte-cron and airbyte-worker starts at line 2824

Noticeable errors on Mac Mac-installation-log.docx :

1. Unable to connect to SQL database. (see line 119 in the Mac log attached)
2. Failed to initialize custom logger: could not build arguments for function "go.uber.org/fx".
   (*App).constructCustomLogger.func2 (see lines 257-276 re building the logger (repeats at 433 and db connects at 466 - in the Mac log attached)
3. Could not find airbyte.yml file (Line 1926 - Mac log file)
4. Debug loop starts at line 1971 - attached Mac log file)

[marcosmarxm]

Can you upload the file instead of pasting the logs unformatted here? What version are you using right now?

[MFIHRI]

@marcosmarxm :

I updated the description above with the logs.

It seems docker-compose up mechanism doesn't handle all exceptions well.
Some configuration file gets created on the fly, container stops/starts for some reason, writing lost and attempting the process will only lead to a loop. Plus, startup dependencies between containers is now broken.
You can only retry if you had set up volumes, just a thought .....