Summary
Error encountered while connecting ClickHouse as a destination to PostgreSQL source, indicating a connection timeout issue with HikariCP.
Question
Hey all
I want to connect clickhouse as a destination against postgres (source) but throw an error like,
Configuration check failed Could not connect with provided configuration. java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 60003ms (total=0, active=0, idle=0, waiting=0)
Please suggest some better solutions
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['clickhouse', 'postgres', 'connection-error', 'hikaricp', 'timeout']
Usually this error means Airbyte server couldn’t access your database. From this snippet it isn’t possible to know if was caused by postgres or clickhouse. Please share the complete sync log.
Hii <@U01MMSDJGC9>,
Very good afternoon
I am stuck in an internal server issue
I installed airbyte through github remote repo and run all docker containers through .sh file.
When I am going to create the source for syncing it throws always an error, providing the stack trace as follows,
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) Caused by: io.temporal.failure.ApplicationFailure: message=‘Unexpected error while getting checking connection.’, type=‘io.airbyte.workers.exception.WorkerException’, nonRetryable=false at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:135) at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:44) at io.airbyte.workers.temporal.TemporalAttemptExecution.get(TemporalAttemptExecution.java:138) at io.airbyte.workers.temporal.check.connection.CheckConnectionActivityImpl.lambda$runWithJobOutput$1(CheckConnectionActivityImpl.java:229) at io.airbyte.commons.temporal.HeartbeatUtils.withBackgroundHeartbeat(HeartbeatUtils.java:57) … 14 more Caused by: io.temporal.failure.ApplicationFailure: message=‘/tmp/workspace/6eded269-83cd-4157-99a6-77939a40e747/0’, type=‘io.airbyte.workers.exception.WorkerException’, nonRetryable=false at io.airbyte.workers.process.DockerProcessFactory.create(DockerProcessFactory.java:191) at io.airbyte.workers.process.AirbyteIntegrationLauncher.check(AirbyteIntegrationLauncher.java:147) at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:71) … 18 more Caused by: io.temporal.failure.ApplicationFailure: message=‘/tmp/workspace/6eded269-83cd-4157-99a6-77939a40e747/0’, type=‘java.nio.file.NoSuchFileException’, nonRetryable=false at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:438) at java.base/java.nio.file.Files.createDirectory(Files.java:699) at io.airbyte.workers.process.DockerProcessFactory.create(DockerProcessFactory.java:121) … 20 more
What I observed, it tells for NoSuchFileException so I created the log folder and gave rights on my local machine and triggered the source button then again it tried to find a newer log folder and raised the same error. I found it is an internal server error, can you please look at it and let me know once you resolve it?
Sorry <@U0836NNGX2R> but you’re only sharing snippets of code. I don’t have full context of your deployment or how you’re running Airbyte. If couldn’t find a workaround in the community please report a new Github issue.
Hii <@U01MMSDJGC9>, hope you are doing absolutely well.
I am stuck in the installation of airbyte through docker,
Can we connect for just 5 min if possible for such queries man?