I have installed airbyte in a kubernetes cluster a...
# replication-ask-ai
b
I have installed airbyte in a kubernetes cluster and connected to an external DB, running in the same cluster. Everything was working correctly, but when I stopped and restarted the cluster I received errors on the server pod, where temporal is unreachable
Copy code
at io.airbyte.server.apis.$SourceDefinitionApiController$Definition.build(Unknown Source) ~[io.airbyte-airbyte-server-0.50.31.jar:?]	at io.micronaut.context.DefaultBeanContext.resolveByBeanFactory(DefaultBeanContext.java:2354) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2305) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2251) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.createRegistration(DefaultBeanContext.java:3016) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.SingletonScope.getOrCreate(SingletonScope.java:80) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.findOrCreateSingletonBeanRegistration(DefaultBeanContext.java:2918) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.loadContextScopeBean(DefaultBeanContext.java:2746) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.initializeContext(DefaultBeanContext.java:1915) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultApplicationContext.initializeContext(DefaultApplicationContext.java:249) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.readAllBeanDefinitionClasses(DefaultBeanContext.java:3326) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.finalizeConfiguration(DefaultBeanContext.java:3684) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultBeanContext.start(DefaultBeanContext.java:341) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.context.DefaultApplicationContext.start(DefaultApplicationContext.java:194) ~[micronaut-inject-3.10.1.jar:3.10.1]	at io.micronaut.runtime.Micronaut.start(Micronaut.java:75) ~[micronaut-context-3.10.1.jar:3.10.1]	at io.micronaut.runtime.Micronaut.run(Micronaut.java:323) ~[micronaut-context-3.10.1.jar:3.10.1]	at io.micronaut.runtime.Micronaut.run(Micronaut.java:309) ~[micronaut-context-3.10.1.jar:3.10.1]	at io.airbyte.server.Application.main(Application.java:15) ~[io.airbyte-airbyte-server-0.50.31.jar:?]Caused by: io.grpc.netty.shaded.io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: Connection refused: airbyte-temporal/10.0.47.144:7233Caused by: java.net.ConnectException: finishConnect(..) failed: Connection refused	at io.grpc.netty.shaded.io.netty.channel.unix.Errors.newConnectException0(Errors.java:155) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.unix.Errors.handleConnectErrno(Errors.java:128) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.unix.Socket.finishConnect(Socket.java:359) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.doFinishConnect(AbstractEpollChannel.java:710) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.finishConnect(AbstractEpollChannel.java:687) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.epollOutReady(AbstractEpollChannel.java:567) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:489) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:397) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at io.grpc.netty.shaded.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[grpc-netty-shaded-1.55.1.jar:1.55.1]	at java.lang.Thread.run(Thread.java:1589) ~[?:?]2023-10-25 14:49:59 WARN i.a.c.t.TemporalUtils(getTemporalClientWhenConnected):250 - Waiting for namespace default to be initialized in temporal...
any idea what could cause this?
k
Based on the error logs you provided, it seems like the Airbyte server is unable to connect to the Temporal service. This could be due to a variety of reasons such as network issues, incorrect configuration, or the Temporal service not being ready yet. Here are a few steps you can take to troubleshoot this issue: 1. Check the status of the Temporal pod: Use the
kubectl get pods
command to check the status of all the pods. Make sure the Temporal pod is running and not in a crash loop. 2. Check the logs of the Temporal pod: Use the
kubectl logs <temporal-pod-name>
command to check the logs of the Temporal pod. This might give you more information about why the Temporal service is not reachable. 3. Check your network configuration: Make sure that the network policies and firewall rules in your Kubernetes cluster allow traffic between the Airbyte server and the Temporal service. 4. Check your Airbyte configuration: In the [Airbyte documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte-db/), it is mentioned that you need to correctly set up the environment variables for the database connection. Make sure these are correctly configured. 5. Restart the Airbyte services: Sometimes, simply restarting the services can solve the issue. You can do this by deleting the deployments and reapplying them as mentioned in the [Airbyte upgrade documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte/). If none of these steps solve your issue, I would recommend reaching out to the Airbyte community on their [Slack channel](https://slack.airbyte.io/) or [creating an issue on GitHub](https://github.com/airbytehq/airbyte/issues/new?assignees=&amp;labels=type%2Fbug&amp;template=bug-report.md&amp;title=).
b
I have already tried to use a new database, to no avail