I have a Airbyte instance on ubuntu VM on a local network which connects to MySQL server in the cloud over SSH, and replicates the database into a posgres instance on the same ubuntu VM.
My sync was working great every 24 hours for last 3 months, but it suddenly started failing since last 3 days. As far as I know nothing has changed in the source as well as destination.
Since I have full control over my Ubuntu VM, I tried restarting the Airbyte service as well as restarting the VM itself, but nothing has worked so far and I’m still getting sync errors.
Can someone figure out what is hapenning here?
- Is this your first time deploying Airbyte?: No
- OS Version / Instance: Ubuntu
- Memory / Disk: 32Gb / 1 Tb
- Deployment: Local
- Airbyte Version: What version are you using now? 0.35.45-alpha
- Source: MySQL (0.5.11)
- Destination: Postgres (0.3.20)
- Step: The issue is happening whenever I try to sync the databases
Here is the log
logs-219.txt (85.0 KB)
Did you operate any kind of maintenance on your VM that could have deleted some files in the paths mounted and used by Airbyte volumes?
I found the following error in your logs:
2022-06-16 16:39:25 e[43mdestinatione[0m > Caused by: java.nio.file.NoSuchFileException: destination_config.json 2022-06-16 16:39:25 e[43mdestinatione[0m > at sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
Airbyte stores your destination configuration as a JSON file and this file has disappeared. I’d suggest trying to update and resave your destination configuration in the UI, or recreating a new destination. It will hopefully solve your problem.
Let me know if it helped.
Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.