airbyte-workload-api-server-svc: Name or service not known @kapa.ai using airbyte 1.1.0 with external DB

Hmm, I don't know enough to give you a confident answer yet. The knowledge sources provided do not contain specific information about the error "airbyte-workload-api-server-svc: Name or service not known" when using Airbyte 1.1.0 with an external database. However, I can provide some general guidance on how to connect Airbyte to an external database. You need to edit the environment variables declared in the

.env

file to configure Airbyte services with the new database. The variables include

DATABASE_USER

,

DATABASE_PASSWORD

,

DATABASE_HOST

,

DATABASE_PORT

,

DATABASE_DB

, and

DATABASE_URL

[source](https://docs.airbyte.com/operator-guides/configuring-airbyte-db#connecting-to-an-external-postgres-database). If you're deploying Airbyte on Kubernetes, you need to add external database details to your

values.yaml

file. This disables the default internal Postgres database (

airbyte/db

), and configures the external Postgres database [source](https://docs.airbyte.com/enterprise-setup/implementation-guide#configuring-the-airbyte-database). If you're still facing issues, I recommend checking the Airbyte [documentation](https://docs.airbyte.io/) or reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io/).

at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.kt:131) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.RouteSelector.next(RouteSelector.kt:73) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:205) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at io.airbyte.api.client.UserAgentInterceptor.intercept(UserAgentInterceptor.kt:34) ~[io.airbyte.airbyte-api-commons-1.1.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at io.airbyte.api.client.auth.AirbyteAuthHeaderInterceptor.intercept(AirbyteAuthHeaderInterceptor.kt:28) ~[io.airbyte.airbyte-api-commons-1.1.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at io.airbyte.workload.api.client.auth.WorkloadApiAuthenticationInterceptor.intercept(WorkloadApiAuthenticationInterceptor.kt:36) ~[io.airbyte.airbyte-api-workload-api-1.1.0.jar:?] at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201) ~[okhttp-4.12.0.jar:?] at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154) ~[okhttp-4.12.0.jar:?] at dev.failsafe.okhttp.FailsafeCall.lambda$execute$0(FailsafeCall.java:117) ~[failsafe-okhttp-3.3.2.jar:3.3.2] at dev.failsafe.Functions.lambda$get$0(Functions.java:46) ~[failsafe-3.3.2.jar:3.3.2] at dev.failsafe.internal.RetryPolicyExecutor.lambda$apply$0(RetryPolicyExecutor.java:74) ~[failsafe-3.3.2.jar:3.3.2] at dev.failsafe.SyncExecutionImpl.executeSync(SyncExecutionImpl.java:187) ~[failsafe-3.3.2.jar:3.3.2] at dev.failsafe.CallImpl.execute(CallImpl.java:33) ~[failsafe-3.3.2.jar:3.3.2] at dev.failsafe.okhttp.FailsafeCall.execute(FailsafeCall.java:121) ~[failsafe-okhttp-3.3.2.jar:3.3.2] at io.airbyte.workload.api.client.generated.WorkloadApi.workloadCreateWithHttpInfo(WorkloadApi.kt:1845) ~[io.airbyte.airbyte-api-workload-api-1.1.0.jar:?] at io.airbyte.workload.api.client.generated.WorkloadApi.workloadCreate(WorkloadApi.kt:218) ~[io.airbyte.airbyte-api-workload-api-1.1.0.jar:?] at io.airbyte.workers.sync.WorkloadClient.createWorkload(WorkloadClient.kt:37) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?] at io.airbyte.workers.sync.WorkloadClient.runWorkloadWithCancellationHeartbeat$lambda$4(WorkloadClient.kt:117) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?] at io.airbyte.commons.temporal.HeartbeatUtils.withBackgroundHeartbeat(HeartbeatUtils.java:57) ~[io.airbyte-airbyte-commons-temporal-core-1.1.0.jar:?] ... 15 more 2024-10-22 165846 ERROR i.a.w.t.FailureConverter(getFailureReason-Q2Q30fc):31 - exception classified as NOT_A_TIMEOUT @kapa.ai

A message from kapa.ai

Based on the provided knowledge sources, it seems like you're encountering an issue with the OkHttp library used in Airbyte. The error stack trace indicates that the application is trying to establish a connection but is failing to do so. The error stack trace shows that the application is trying to execute a call using OkHttp, but it's failing at the

ExchangeFinder.findConnection

method. This method is responsible for finding a suitable connection to carry out the network request. If it's unable to find a suitable connection, it throws an exception. The error message

java.net.SocketTimeoutException: Connect timed out

suggests that the application is unable to establish a connection within the specified timeout period. This could be due to network issues, firewall settings, or server unavailability. The error message

ERROR i.a.w.t.FailureConverter(getFailureReason-Q2Q30fc):31 - exception classified as NOT_A_TIMEOUT

suggests that the exception was not classified as a timeout, which might indicate that the issue is not related to network latency but could be due to other factors. Unfortunately, without more specific information about your setup and the context in which this error is occurring, it's hard to provide a more precise answer. If you're still facing this issue, I recommend checking the Airbyte [documentation](https://docs.airbyte.io/) or reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io/) for more specific guidance.