https://linen.dev logo
Join Slack
Powered by
Hello I am getting an error 2025-12-11 19:10:49 w...
# replication-troubleshooting
d
Hello I am getting an error 2025-12-11 191049 warn Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running?
k
This warning is raised by the Airbyte connector sidecar (
ConnectorWatcher
) when it does not see the expected output files from a connector within 9 minutes, so it fails the workload and exits with code 2. [[Sidecar timeout](https://github.com/airbytehq/airbyte/issues/48855); [MySQL check timeout](https://github.com/airbytehq/airbyte/issues/52075)] From the available issues, there are two main patterns: 1. The connector never finishes / hangs or fails silently In the MySQL example, the check job runs for 9 minutes with no output, then the sidecar logs exactly your message and fails the workload. [[MySQL check timeout](https://github.com/airbytehq/airbyte/issues/52075)] In this case, you need to inspect the connector pod/container logs (the 
START CHECK
/ 
START DISCOVER
logs, etc.) to see why it is not producing output. 2. Configuration error causing the connector to misbehave quickly, but the platform only sees “no output” In the Zendesk Support example, the platform shows the same 9‑minute timeout error, but the root cause was a misconfigured connector: the user put the full Zendesk URL instead of just the subdomain. Fixing the configuration resolved the issue. [[Zendesk timeout](https://github.com/airbytehq/airbyte/issues/54684)] Given the knowledge sources, I can’t see your exact connector or logs, so I can’t say precisely what is wrong in your case. However, based on them, here’s what you should do: 1. Check connector configuration carefully - For Zendesk Support, ensure the “subdomain” field is only the subdomain (e.g. 
mycompany
), not the full URL (
<https://mycompany.zendesk.com>
). [[Zendesk timeout](https://github.com/airbytehq/airbyte/issues/54684)] - For other connectors, double‑check host, port, credentials, and any special fields per the connector’s docs. 2. Inspect connector pod logs - Look for lines like 
----- START CHECK -----
or 
----- START DISCOVER -----
and any errors right after them. [[Zendesk timeout](https://github.com/airbytehq/airbyte/issues/54684); [Sidecar timeout](https://github.com/airbytehq/airbyte/issues/48855)] - If the connector crashes quickly, you’ll see an error there even though the sidecar only reports the 9‑minute timeout. 3. Confirm the workload actually starts - In the Zendesk issue, the platform logs show the workload being claimed, built, launched, and then later failed with the timeout. [[Zendesk timeout](https://github.com/airbytehq/airbyte/issues/54684)] - If no pod is ever running for the workload, that can also lead to the same message. [[Zendesk timeout](https://github.com/airbytehq/airbyte/issues/54684)] Because the knowledge sources don’t include a general configuration or knob to change this 9‑minute timeout (only a request to make it configurable), I can’t provide a supported way to increase it. [[Sidecar timeout](https://github.com/airbytehq/airbyte/issues/48855)] If you can share which connector you’re using and a snippet of its pod logs around 
START CHECK
/ 
START DISCOVER
, I can help interpret them against these patterns.
d
Copy code
2025-12-11 19:01:49 info ----- START CHECK -----
2025-12-11 19:01:49 info 
2025-12-11 19:01:49 info Workload successfully transitioned to running state
2025-12-11 19:10:49 info Output file jobOutput.json found
2025-12-11 19:10:49 info Reading messages from protocol version 0.2.0
2025-12-11 19:10:49 info INFO main i.m.c.e.DefaultEnvironment(<init>):168 Established active environments: [k8s, cloud, cli, source, connector]
2025-12-11 19:10:49 warn WARN main c.k.j.j.JsonSchemaGenerator$MyJsonFormatVisitorWrapper(expectAnyFormat):725 Not able to generate jsonSchema-info for type: [simple type, class com.fasterxml.jackson.databind.JsonNode] - probably using custom serializer which does not override acceptJsonFormatVisitor
2025-12-11 19:10:49 info INFO main i.a.c.AirbyteConnectorRunnable(run):35 Executing class io.airbyte.cdk.check.CheckOperation operation.
2025-12-11 19:10:49 info INFO main i.a.c.c.CheckOperation(execute):33 Parsing connector configuration JSON object.
2025-12-11 19:10:49 info INFO main i.a.c.c.CheckOperation(execute):35 Building internal connector configuration object.
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlServerSourceConfigurationFactory(makeWithoutExceptionHandling):237 maxConcurrency: null. socket paths: 0
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlServerSourceConfigurationFactory(makeWithoutExceptionHandling):247 Effective concurrency: 1
2025-12-11 19:10:49 info INFO main i.a.c.c.CheckOperation(execute):37 Connecting for config check.
2025-12-11 19:10:49 info INFO main i.a.c.j.JdbcConnectionFactory(get):44 Creating new connection for 'jdbc:<sqlserver://10.1.65.12:49884>;databaseName=basion'.
2025-12-11 19:10:49 info INFO main i.a.c.c.CheckOperation(connectionCheck):63 Querying all stream names and namespaces.
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedTableNames$2(invoke):109 Querying SQL Server table names for catalog discovery.
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedTableNames$2(invoke):117 No schemas explicitly configured, discovering all non-system schemas in the database.
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedTableNames$2(invoke):154 Discovered 198 table(s) in SQL Server database 'basion'.
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedColumnMetadata$2(invoke):167 Querying SQL Server column names for catalog discovery.
2025-12-11 19:10:49 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedColumnMetadata$2(invoke):191 Querying columns for all schemas.
2025-12-11 19:10:49 warn Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running?
2025-12-11 19:10:49 info Failing workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_48500e7d-e44a-413b-993a-c9f0f3df9e3f_0_check.
2025-12-11 19:10:49 info Deliberately exiting process with code 2.
So I think in my Airbyte 2.0.1 deployment the 9‑minute limit is hardcoded in the connector sidecar and has no supported knob to increase it, so the platform will always fail the workload if the connector takes longer than 9 minutes to emit output.
9 Views
Open in Slack
PreviousNext
Powered by