@kapa.ai mysql connector sync job pullig 0 rows, I cannot open the logs

You’re running into a known class of issues where a sync “succeeds” but 0 records are read/written. Since you can’t open the logs, you’ll need to first get access to them; without logs, it’s not possible to see the exact cause. 1. Get to the logs (required first step) If you’re on Airbyte (OSS or Cloud) UI: 1. Go to the connection. 2. Open the Job history tab. 3. For the latest sync, click the three dots (…) on the right. 4. Try: ◦ View logs (in-app viewer), or ◦ Download logs (to inspect locally). [Browsing logs] If “View logs” doesn’t open, still try Download logs from the same menu. If the job had multiple attempts, the downloaded file will contain all of them. [Browsing logs] If you’re on OSS and the UI options fail entirely, you may need to read logs directly from the Docker/Kubernetes volumes (the docs mention “additional logs outside of the UI” but don’t give exact commands). [Browsing logs] 2. Common reasons for “0 rows” with MySQL Once you can see the logs, look for: • Permission issues / CDC not allowed – e.g. missing

REPLICATION SLAVE

/

REPLICATION CLIENT

/

SELECT

grants can cause 0 records read with CDC. Granting the proper privileges fixed a similar “Total records read: 0” case:GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT ON . TO 'airbyte'@'%';[MySQL v8.0 to Clickhouse] • Connection / network errors – some jobs show 0 records but actually fail due to connection timeouts (e.g. HikariPool timeouts, SSH tunnel issues). [Sync shows succeeded after 0 records] • Resource / pod issues – in some cases, the platform logs show resource errors (e.g. replication pod can’t start) and the sync appears to do nothing. [MSSQL→MSSQL 0 rows] • MySQL-specific quirks – e.g. DigitalOcean binlog cleanup, MariaDB CDC limitations, etc., but those usually affect CDC/incremental rather than causing 0 rows on a basic full refresh. [MySQL troubleshooting] 3. What you can do next 1. Get any form of logs (UI viewer or download). If that’s impossible, mention: ◦ Are you on Cloud or OSS? ◦ How you deployed (Docker, abctl, Kubernetes). 1. Once you have logs, search for: ◦

Error

,

Exception

,

Fail

◦

Total records read

◦

HikariPool

,

ResourceConstraintException

,

OutOfMemoryError

,

Unable establish a connection

1. If you can share a redacted snippet of the logs (no hostnames/passwords), I can help interpret the exact cause. Right now, the knowledge sources don’t give a way to fix “0 rows and cannot open logs” without first regaining access to the job logs, so the key step is to use the Job History menu (View/Download logs) or, on OSS, read them from the underlying volumes as described in the logging guide. [Browsing logs] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.