Hey all, having a few problems with Airbyte on EC2 with a Redshift destination. I’m loading our MySQL database in and it’s taking a very long time for ~20GB data and then fails. I started running it at 11:30am BST yesterday and it failed at 19:30pm. Looking at the logs I can’t tell what’s failing because I’m getting

Completed successfully

from the dbt output. As it failed though, it’s on its third attempt since, close to 24 hours after I first tried running it. Anyone come across this before? Airbyte is running on a t2.large instance and the Redshift cluster is a 2 node dc2.large. Screenshots attached of “failing” logs and the long run times

can you post some full logs files? You can download them from the UI and attach it below in this slack thread

@Phil Marius Check the full log to be sure there was no failure in-between especially

Zero value prohibited

Found it

Zero value date prohibited

. Cheers for pointing that out, does that mean there’s a NULL value in a date column?

You can try the suggestions from this other thread: https://airbytehq.slack.com/archives/C01MFR03D5W/p1626943618162300?thread_ts=1626941314.158500&cid=C01MFR03D5W

@Phil Marius You can try the suggested option by @Chris (deprecated profile) though it didn't work for me for tables that I have null in the date field

Apologies for not getting back sooner, trying this now

@Phil Marius let me know if this param work for you

It worked! However it said 0 bytes / no records were copied over. Redshift isn’t showing anything aside from the tables created

did you reset your connection?