https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> please check
# replication-troubleshooting
d
@kapa.ai please check
k
The knowledge sources you provided mostly show log excerpts and API references where “check” appears (e.g., source configuration checks, health checks, and connector availability checks), but they do not include a specific question or problem description from you beyond “please check.” [[Run Check Source](https://docs.airbyte.com/ai-agents/embedded/api-reference/create-integrations-sources-check); [Status Check Source](https://docs.airbyte.com/ai-agents/embedded/api-reference/get-integrations-sources-check-id-status)] Because of that, I’m not able to determine what you want me to check (a specific connector error, an API call, configuration, etc.). Here are a few concrete things you might be referring to, with the relevant endpoints: - To run a source config check (create a check job): 
POST /api/v1/integrations/sources/check
[[Run Check Source](https://docs.airbyte.com/ai-agents/embedded/api-reference/create-integrations-sources-check)] - To run a check for an existing source: 
POST /api/v1/integrations/sources/:id/check
[[Run Check Source Update](https://docs.airbyte.com/ai-agents/embedded/api-reference/create-integrations-sources-id-check)] - To get the status of a check: 
GET /api/v1/integrations/sources/check/:id/status
or 
GET /api/v1/embedded/sources/check/:id/status
[[Status Check Source](https://docs.airbyte.com/ai-agents/embedded/api-reference/get-integrations-sources-check-id-status); [Embedded Status Check](https://docs.airbyte.com/ai-agents/embedded/api-reference/get-embedded-sources-check-id-status)] - To check the embedded service health: 
GET /api/v1/internal/health/check
[[Health Check](https://docs.airbyte.com/ai-agents/embedded/api-reference/get-internal-health-check)] Please clarify what you’d like me to check (for example: “check why my Postgres source fails SSL validation” or “check how to interpret this Bad request error for Facebook Page source”), and I’ll use the provided knowledge to give a focused answer.
d
In which Airbyte version was this 9‑minute sidecar timeout made configurable or increased, and what is the recommended upgrade path from 2.0.1 for this issue?”
2025-12-11 193413 info APPLY Stage: BUILD — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info APPLY Stage: CLAIM — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info Claimed: true for workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check via API in dataplane a7c2bcfa-3e3c-4b31-b2d4-da6e96ed3b0d (d3e9bb6f-a969-477d-af64-0e0f0790648c) 2025-12-11 193413 info APPLY Stage: LOAD_SHED — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info APPLY Stage: CHECK_STATUS — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info No pod found running for workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check 2025-12-11 193413 info APPLY Stage: MUTEX — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info No mutex key specified for workload: b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check. Continuing... 2025-12-11 193413 info APPLY Stage: ARCHITECTURE — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info APPLY Stage: LAUNCH — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info [initContainer] image: airbyte/workload-init-container:2.0.1 resources: ResourceRequirements(claims=[], limits={}, requests={}, additionalProperties={}) 2025-12-11 193417 info Attempting to update workload: b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check to LAUNCHED. 2025-12-11 193417 info Pipeline completed for workload: b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check. 2025-12-11 193418 info 2025-12-11 193419 info Transitioning workload to running state 2025-12-11 193419 info ----- START CHECK ----- 2025-12-11 193419 info 2025-12-11 193419 info Workload successfully transitioned to running state 2025-12-11 194319 info Output file jobOutput.json found 2025-12-11 194319 info Reading messages from protocol version 0.2.0 2025-12-11 194319 info INFO main i.m.c.e.DefaultEnvironment(<init>):168 Established active environments: [k8s, cloud, cli, source, connector] 2025-12-11 194319 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 194319 info INFO main i.a.c.AirbyteConnectorRunnable(run):35 Executing class io.airbyte.cdk.check.CheckOperation operation. 2025-12-11 194319 info INFO main i.a.c.c.CheckOperation(execute):33 Parsing connector configuration JSON object. 2025-12-11 194319 info INFO main i.a.c.c.CheckOperation(execute):35 Building internal connector configuration object. 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlServerSourceConfigurationFactory(makeWithoutExceptionHandling):237 maxConcurrency: null. socket paths: 0 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlServerSourceConfigurationFactory(makeWithoutExceptionHandling):247 Effective concurrency: 1 2025-12-11 194319 info INFO main i.a.c.c.CheckOperation(execute):37 Connecting for config check. 2025-12-11 194319 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 194319 info INFO main i.a.c.c.CheckOperation(connectionCheck):63 Querying all stream names and namespaces. 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedTableNames$2(invoke):109 Querying SQL Server table names for catalog discovery. 2025-12-11 194319 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 194319 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 194319 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedColumnMetadata$2(invoke):167 Querying SQL Server column names for catalog discovery. 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedColumnMetadata$2(invoke):191 Querying columns for all schemas. 2025-12-11 194319 warn Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running? 2025-12-11 194319 info Failing workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check. 2025-12-11 194319 info Deliberately exiting process with code 2.
@kapa.ai please check
k
A message from kapa.ai
The knowledge sources you provided do not contain enough information to understand what you want me to “check.” They describe: - How to get the status of a source configuration check via the Embedded API: 
GET /api/v1/integrations/sources/check/:id/status
(requires bearer access token). [[Status check source](https://docs.airbyte.com/ai-agents/embedded/api-reference/get-integrations-sources-check-id-status)] - How to review and troubleshoot connection status and sync errors in the Airbyte UI (Status page, Streams status, Records loaded, error types, etc.). [[Connection status](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-status); [Connection troubleshooting](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-status#connection-troubleshooting)] But there is no specific resource ID, error message, connection, or configuration in your question. Please specify what you want checked, for example: - “Check the status of a source check job with ID 
<id>
via the API” - “Check why my connection shows Failed on the Status page” - “Check how to interpret a particular error message” Once you provide that detail, I can map it to the relevant docs and give a concrete answer.
d
@kapa.ai 2025-12-11 193413 info APPLY Stage: BUILD — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info APPLY Stage: CLAIM — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info Claimed: true for workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check via API in dataplane a7c2bcfa-3e3c-4b31-b2d4-da6e96ed3b0d (d3e9bb6f-a969-477d-af64-0e0f0790648c) 2025-12-11 193413 info APPLY Stage: LOAD_SHED — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info APPLY Stage: CHECK_STATUS — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info No pod found running for workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check 2025-12-11 193413 info APPLY Stage: MUTEX — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info No mutex key specified for workload: b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check. Continuing... 2025-12-11 193413 info APPLY Stage: ARCHITECTURE — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info APPLY Stage: LAUNCH — (workloadId=b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check) 2025-12-11 193413 info [initContainer] image: airbyte/workload-init-container:2.0.1 resources: ResourceRequirements(claims=[], limits={}, requests={}, additionalProperties={}) 2025-12-11 193417 info Attempting to update workload: b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check to LAUNCHED. 2025-12-11 193417 info Pipeline completed for workload: b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check. 2025-12-11 193418 info 2025-12-11 193419 info Transitioning workload to running state 2025-12-11 193419 info ----- START CHECK ----- 2025-12-11 193419 info 2025-12-11 193419 info Workload successfully transitioned to running state 2025-12-11 194319 info Output file jobOutput.json found 2025-12-11 194319 info Reading messages from protocol version 0.2.0 2025-12-11 194319 info INFO main i.m.c.e.DefaultEnvironment(<init>):168 Established active environments: [k8s, cloud, cli, source, connector] 2025-12-11 194319 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 194319 info INFO main i.a.c.AirbyteConnectorRunnable(run):35 Executing class io.airbyte.cdk.check.CheckOperation operation. 2025-12-11 194319 info INFO main i.a.c.c.CheckOperation(execute):33 Parsing connector configuration JSON object. 2025-12-11 194319 info INFO main i.a.c.c.CheckOperation(execute):35 Building internal connector configuration object. 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlServerSourceConfigurationFactory(makeWithoutExceptionHandling):237 maxConcurrency: null. socket paths: 0 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlServerSourceConfigurationFactory(makeWithoutExceptionHandling):247 Effective concurrency: 1 2025-12-11 194319 info INFO main i.a.c.c.CheckOperation(execute):37 Connecting for config check. 2025-12-11 194319 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 194319 info INFO main i.a.c.c.CheckOperation(connectionCheck):63 Querying all stream names and namespaces. 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedTableNames$2(invoke):109 Querying SQL Server table names for catalog discovery. 2025-12-11 194319 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 194319 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 194319 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedColumnMetadata$2(invoke):167 Querying SQL Server column names for catalog discovery. 2025-12-11 194319 info INFO main i.a.i.s.m.MsSqlSourceMetadataQuerier$memoizedColumnMetadata$2(invoke):191 Querying columns for all schemas. 2025-12-11 194319 warn Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running? 2025-12-11 194319 info Failing workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_b052588b-a23c-4dba-a1e7-67536805957b_0_check. 2025-12-11 194319 info Deliberately exiting process with code 2.
k
A message from kapa.ai
The knowledge sources show this exact pattern of logs and failure message (“Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running?”) occurring when a connector check or discover runs longer than the platform’s sidecar timeout. [[MySQL check issue](https://github.com/airbytehq/airbyte/issues/52075); [Sidecar timeout issue](https://github.com/airbytehq/airbyte/issues/48855)] In your logs, the MSSQL source: - Connects successfully - Discovers 198 tables - Starts querying column metadata for all schemas - Then hits the 9‑minute timeout and the workload is failed by the platform sidecar So: - The connector itself is working and is in the middle of catalog discovery. - The failure is due to the platform timing out before the connector finishes, not an authentication or network error. Airbyte docs describe a similar situation for large schemas and recommend increasing the timeout for discovery/check operations by adjusting server timeouts in your Helm values (for large database sources). [[Schema discovery timeouts 1.8](https://docs.airbyte.com/platform/1.8/enterprise-setup/scaling-airbyte#schema-discovery-timeouts); [Schema discovery timeouts next](https://docs.airbyte.com/platform/next/enterprise-setup/scaling-airbyte#schema-discovery-timeouts)] For Helm chart v2, for example:
Copy code
yaml server:   httpIdleTimeout: 20m   extraEnv:     - name: READ_TIMEOUT       value: 30m
For Helm chart v1:
Copy code
yaml server:   extraEnv:     - name: HTTP_IDLE_TIMEOUT       value: 20m     - name: READ_TIMEOUT       value: 30m
These examples are specifically documented for long‑running schema discovery; your MSSQL check is effectively doing that (198 tables, all columns), so increasing these timeouts should allow the check to complete instead of being killed at 9 minutes. [[Schema discovery timeouts enterprise](https://docs.airbyte.com/platform/enterprise-setup/scaling-airbyte#schema-discovery-timeouts)] If, after increasing timeouts, the job still never finishes, the knowledge sources do not provide further MSSQL‑specific troubleshooting steps, so I can’t say more with confidence.
d
@kapa.ai its for MSSQL
2 Views
Open in Slack
PreviousNext
Powered by