David Backx
12/01/2025, 7:12 AMeadFromSource: exception caught
java.lang.IllegalStateException: Source process is still alive, cannot retrieve exit value.
The source is a MSSQL database and the destination is S3. It all started when i had wrong permissions on the database and when that was fixed i started getting these errors. Its reading almost every try between 300MB-370MB. What could be the issue?kapa.ai
12/01/2025, 7:12 AMreadFromSource: exception caught java.lang.IllegalStateException: Source process is still alive, cannot retrieve exit value. is closely related to a class of issues where Airbyte is unable to properly stop or retrieve the status of the source connector process. This is often accompanied by errors like "No exit code found" or "Source cannot be stopped!" and is seen in various connectors, including MSSQL and others. From the forum and GitHub issues, several possible causes and contributing factors are mentioned: 1. Resource Constraints or Process Hangs: In some cases, the source connector process may hang or fail to terminate properly, especially after handling large data volumes or after encountering previous errors. This can prevent Airbyte from retrieving the exit code, resulting in the error you see. For example, in one case with large batch updates in MSSQL, the process failed to close properly after reading was finished, leading to a similar error ([Forum Post: Source MSSQL - CDC incremental load failed](https://discuss.airbyte.io/t/4013)). 2. Previous Permission Issues: Since you mentioned that the issue started after fixing database permissions, it's possible that the connector process encountered an unrecoverable state during the period of incorrect permissions. Even after fixing the permissions, the connector or Airbyte worker may be in a "bad state" or have cached/partial state from previous failed runs. 3. Large Data Volumes: The logs in similar issues show that when syncing large amounts of data (hundreds of MBs or more), the process is more likely to hang or fail to terminate cleanly, especially if there are resource constraints (memory, CPU) or network issues ([destination-s3-data-lake sync stalling](https://github.com/airbytehq/airbyte/issues/56926)). What you can try: - Restart Airbyte and the Connector Pods/Containers: Fully restart your Airbyte instance and ensure all connector containers are stopped and restarted. This can clear any lingering processes or bad state. - Check Resource Allocation: Ensure your Airbyte deployment (especially if on Kubernetes or Docker) has sufficient memory and CPU allocated, as resource exhaustion can cause connector processes to hang. - Review Database Permissions: Double-check that the MSSQL user has all required permissions for both reading data and any CDC (Change Data Capture) operations, if used. - Check for Stuck or Zombie Processes: If you have shell access to the host, check for any lingering connector processes that may not have terminated and kill them if necessary. - Review Airbyte and Connector Logs: Look for any additional errors or stack traces in the logs that might indicate why the process is not terminating. If the problem persists after these steps, it may be a bug or edge case in the connector or Airbyte platform itself, especially given the similarity to other reported issues. In that case, consider opening a GitHub issue with detailed logs and your configuration, referencing similar issues for context ([example issue](https://discuss.airbyte.io/t/4013)). I'm sorry, but the knowledge sources do not provide a definitive root cause or fix for this exact error, but the above steps are based on closely related issues and recommended troubleshooting actions.David Backx
12/01/2025, 7:29 AMkapa.ai
12/01/2025, 7:29 AMkapa.ai
12/01/2025, 7:30 AMvalues.yaml) to better match your workload, but ultimately, if the instance is maxed out, increasing instance size is necessary [Scaling Airbyte After Installation](https://docs.airbyte.com/platform/enterprise-setup/scaling-airbyte). In summary: - Restarting may help briefly, but will not solve high CPU usage. - To reliably handle large data volumes, you should upsize your EC2 instance and/or adjust Airbyte resource settings. - Monitor CPU and memory usage, and scale resources as your data integration needs grow.David Backx
12/01/2025, 7:30 AMkapa.ai
12/01/2025, 7:30 AMkapa.ai
12/01/2025, 7:31 AM